🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`accelerant.tech`

DNSSEC	⚠️ Not signed
NS	`harleigh.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:263a^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`harleigh.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c23a^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`harleigh.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:223a^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`harleigh.ns.cloudflare.com`
		A	108.162.194.58^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`harleigh.ns.cloudflare.com`
		A	162.159.38.58^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`harleigh.ns.cloudflare.com`
		A	172.64.34.58^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`harleigh.ns.cloudflare.com`
NS	`vicky.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c45^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`vicky.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c345^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`vicky.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2345^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`vicky.ns.cloudflare.com`
		A	108.162.195.69^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`vicky.ns.cloudflare.com`
		A	162.159.44.69^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`vicky.ns.cloudflare.com`
		A	172.64.35.69^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`vicky.ns.cloudflare.com`
MX	`route1.mx.cloudflare.net` ⭐
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁵⁶⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁵⁶⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`harleigh.ns.cloudflare.com`dns@cloudflare.com serial=2414079699

`tech`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1788645538

Same first word

Similar names

Previous names

Next names

DNS History

11 records (5 active, 6 former)

●NSharleigh.ns.cloudflare.com2026-08-17 → 2026-09-05 · 3 obs

○ 2017-06-17 08:50:50
● 2026-08-17 17:20:06
● 2026-09-05 22:03:08

○NSns01.cashparking.com2016-12-12 → 2017-06-17 · 4 obs

● 2016-12-12 23:55:12
● 2017-06-17 08:50:50
○ 2026-08-17 17:20:06
○ 2026-09-05 22:03:08

●NSvicky.ns.cloudflare.com2026-08-17 → 2026-09-05 · 3 obs

○ 2017-06-17 08:50:50
● 2026-08-17 17:20:06
● 2026-09-05 22:03:08

○MX(root)2017-06-17 → 2017-06-17 · 4 obs

○ 2016-12-12 23:55:12
● 2017-06-17 08:50:50
○ 2026-08-17 17:20:06
○ 2026-09-05 22:03:08

○MX102017-06-17 → 2017-06-17 · 4 obs

○ 2016-12-12 23:55:12
● 2017-06-17 08:50:50
○ 2026-08-17 17:20:06
○ 2026-09-05 22:03:08

○MXmailstore1.secureserver.net2016-12-12 → 2016-12-12 · 3 obs

● 2016-12-12 23:55:12
○ 2017-06-17 08:50:50
○ 2026-09-05 22:03:08

●MXroute1.mx.cloudflare.net2026-08-17 → 2026-09-05 · 3 obs

○ 2017-06-17 08:50:50
● 2026-08-17 17:20:06
● 2026-09-05 22:03:08

●MXroute2.mx.cloudflare.net2026-08-17 → 2026-09-05 · 3 obs

○ 2017-06-17 08:50:50
● 2026-08-17 17:20:06
● 2026-09-05 22:03:08

●MXroute3.mx.cloudflare.net2026-08-17 → 2026-09-05 · 3 obs

○ 2017-06-17 08:50:50
● 2026-08-17 17:20:06
● 2026-09-05 22:03:08

○MXsmtp.secureserver.net2016-12-12 → 2016-12-12 · 3 obs

● 2016-12-12 23:55:12
○ 2017-06-17 08:50:50
○ 2026-09-05 22:03:08

○A184.168.221.962016-12-12 → 2017-06-17 · 4 obs

● 2016-12-12 23:55:12
● 2017-06-17 08:50:50
○ 2026-08-17 17:20:06
○ 2026-09-05 22:03:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tech	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	8 records
accelerant.tech	vicky.ns.cloudflare.com, harleigh.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.195.69

NS records: vicky.ns.cloudflare.com, harleigh.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for accelerant.tech (unsigned zone)

⏱️ Timing

Total: 996ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`harleigh.ns.cloudflare.com, vicky.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 15), route2.mx.cloudflare.net (pri: 56)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`harleigh.ns.cloudflare.com dns.cloudflar`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns10.trs-dns.info, ns10.trs-dns.org, ns01.trs-dns.net...)

Analysis

Name Servers

accelerant.tech is delegated to two name servers: harleigh.ns.cloudflare.com and vicky.ns.cloudflare.com.

accelerant.tech uses the same name servers as several other domains — among them home-trez-eng-log.pages.dev, textochka.ru, trescott.com and two more.

At least some of accelerant.tech's name servers are shared with other domains, for example 5dd587e0bd1819.workers.dev, info3950.workers.dev, bbrd1t.com and two more.

These name servers tend to be used in conjunction with the name servers peyton.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

harleigh.ns.cloudflare.com resolves to 108.162.194.58, 162.159.38.58, 172.64.34.58 and 3 other IP addresses.

vicky.ns.cloudflare.com resolves to 108.162.195.69, 162.159.44.69, 172.64.35.69 and 3 other IP addresses.

Mail Servers

The MX records for accelerant.tech list three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

accelerant.tech has at least partial mail server overlap with other domains such as brodycooper.com, sacosmetics.nl, sevenplay.ca and two more.

Hostnames that resolve to 6 IP addresses:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12, 162.159.205.13 and 3 other IP addresses.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18, 162.159.205.19 and 3 other IP addresses.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24, 162.159.205.25 and 3 other IP addresses.

accelerant.tech - robtex.com

accelerant.tech

tech

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

Name Servers

Mail Servers

`accelerant.tech`

`tech`