`trafficamplify.com`

DNSSEC	⚠️ Not signed
NS	`macy.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:264e^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`macy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c24e^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`macy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:224e^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`macy.ns.cloudflare.com`
		A	108.162.194.78^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`macy.ns.cloudflare.com`
		A	162.159.38.78^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`macy.ns.cloudflare.com`
		A	172.64.34.78^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`macy.ns.cloudflare.com`
NS	`rohin.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c99^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rohin.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c399^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`rohin.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2399^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`rohin.ns.cloudflare.com`
		A	108.162.195.153^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rohin.ns.cloudflare.com`
		A	162.159.44.153^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rohin.ns.cloudflare.com`
		A	172.64.35.153^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rohin.ns.cloudflare.com`
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`
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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`macy.ns.cloudflare.com`dns@cloudflare.com serial=2410348981

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1785799002

Previously MX for

trafficamplify.com

Same first word

trafficamplify.com

DNS History

9 records (5 active, 4 former)

●NSmacy.ns.cloudflare.com2026-07-02 → 2026-08-03 · 3 obs

○ 2017-05-09 05:03:30
● 2026-07-02 08:36:46
● 2026-08-03 23:36:32

○NSns1.ericlouviere.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 05:03:30
○ 2026-07-02 08:36:46
○ 2026-08-03 23:36:32

○NSns2.ericlouviere.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 05:03:30
○ 2026-07-02 08:36:46
○ 2026-08-03 23:36:32

●NSrohin.ns.cloudflare.com2026-07-02 → 2026-08-03 · 3 obs

○ 2017-05-09 05:03:30
● 2026-07-02 08:36:46
● 2026-08-03 23:36:32

●MXroute1.mx.cloudflare.net2026-07-02 → 2026-08-03 · 3 obs

○ 2017-05-09 05:03:30
● 2026-07-02 08:36:46
● 2026-08-03 23:36:32

●MXroute2.mx.cloudflare.net2026-07-02 → 2026-08-03 · 3 obs

○ 2017-05-09 05:03:30
● 2026-07-02 08:36:46
● 2026-08-03 23:36:32

●MXroute3.mx.cloudflare.net2026-07-02 → 2026-08-03 · 3 obs

○ 2017-05-09 05:03:30
● 2026-07-02 08:36:46
● 2026-08-03 23:36:32

○MXtrafficamplify.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 05:03:30
○ 2026-07-02 08:36:46
○ 2026-08-03 23:36:32

○A72.52.169.712017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 05:03:30
○ 2026-07-02 08:36:46
○ 2026-08-03 23:36:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
trafficamplify.com	macy.ns.cloudflare.com, rohin.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.78

NS records: macy.ns.cloudflare.com, rohin.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for trafficamplify.com (unsigned zone)

⏱️ Timing

Total: 119ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`macy.ns.cloudflare.com, rohin.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 26), route1.mx.cloudflare.net (pri: 46)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`macy.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (macy.ns.cloudflare.com, macy.ns.cloudflare.com, macy.ns.cloudflare.com...)

Analysis

Name Servers

trafficamplify.com is served by two delegated name servers, macy.ns.cloudflare.com and rohin.ns.cloudflare.com.

trafficamplify.com uses the same name servers as several other domains — among them viralomat.com, leyaniinc.com, roger3z-vps.online and two more.

trafficamplify.com partially shares its NS delegation with several other domains, including cwyhf.com, myjscode.com, oldi.market and two others.

These name servers regularly co-occur with the name servers kira.ns.cloudflare.com, sage.ns.cloudflare.com and diana.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

macy.ns.cloudflare.com carries IP addresses 108.162.194.78, 162.159.38.78 and 172.64.34.78, with 3 other addresses beyond those.

rohin.ns.cloudflare.com carries IP addresses 108.162.195.153, 162.159.44.153 and 172.64.35.153, with 3 other addresses beyond those.

Mail Servers

trafficamplify.com uses three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

trafficamplify.com has at least partial mail server overlap with other domains such as meslcloud.com, daydreamlabs.com, dev.rt.ht and two more.

Hostnames that resolve to 6 IP addresses:

route1.mx.cloudflare.net carries IP addresses 162.159.205.11, 162.159.205.12 and 162.159.205.13, with 3 other addresses beyond those.

route2.mx.cloudflare.net carries IP addresses 162.159.205.17, 162.159.205.18 and 162.159.205.19, with 3 other addresses beyond those.

route3.mx.cloudflare.net carries IP addresses 162.159.205.23, 162.159.205.24 and 162.159.205.25, with 3 other addresses beyond those.

trafficamplify.com - robtex.com