`trafficmonarch.com`

DNSSEC	⚠️ Not signed
A	203.161.33.68^{🇺🇸 NAMCHEAP-PH203.161.33.0/24}
		PTR	`nc-ph-4326.blazenet.com`
NS	`ns1.trafficmonarch.com` ⭐
		A	203.161.33.68^{🇺🇸 NAMCHEAP-PH203.161.33.0/24}
			PTR	`nc-ph-4326.blazenet.com`
NS	`ns2.trafficmonarch.com`
		A	203.161.33.68^{🇺🇸 NAMCHEAP-PH203.161.33.0/24}
			PTR	`nc-ph-4326.blazenet.com`
MX	`mail.trafficmonarch.com` ⭐
		A	203.161.33.68^{🇺🇸 NAMCHEAP-PH203.161.33.0/24}
			PTR	`nc-ph-4326.blazenet.com`
TXT	`v=spf1 ip4:203.161.33.68 +a +mx +ip4:162.0.217.62 +ip4:162.0.217.68 include:s...`
SOA	`ns1.trafficmonarch.com`hosting-notifications@namecheaphosting.com 2026-03-25 #1

`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=1774416637

📈 Tranco rank: #532,568

Subdomains

ns2.trafficmonarch.com

ns1.trafficmonarch.com

mail.trafficmonarch.com

Same first word

trafficmonarch.com

DNS History

20 records (4 active, 16 former)

○NSdns1.name-services.com2015-12-19 → 2015-12-19 · 4 obs

○ 2015-08-17 15:43:54
● 2015-12-19 09:24:44
○ 2016-03-25 02:23:38
○ 2026-03-25 05:58:36

○NSdns1.namecheaphosting.com2016-03-25 → 2016-09-08 · 5 obs

○ 2015-12-19 09:24:44
● 2016-03-25 02:23:38
● 2016-09-08 05:54:18
○ 2017-12-31 00:17:28
○ 2026-03-25 05:58:36

○NSdns1.stabletransit.com2015-08-17 → 2015-08-17 · 3 obs

● 2015-08-17 15:43:54
○ 2015-12-19 09:24:44
○ 2026-03-25 05:58:36

○NSdns2.name-services.com2015-12-19 → 2015-12-19 · 4 obs

○ 2015-08-17 15:43:54
● 2015-12-19 09:24:44
○ 2016-03-25 02:23:38
○ 2026-03-25 05:58:36

○NSdns2.namecheaphosting.com2016-03-25 → 2016-09-08 · 5 obs

○ 2015-12-19 09:24:44
● 2016-03-25 02:23:38
● 2016-09-08 05:54:18
○ 2017-12-31 00:17:28
○ 2026-03-25 05:58:36

○NSdns2.stabletransit.com2015-08-17 → 2015-08-17 · 3 obs

● 2015-08-17 15:43:54
○ 2015-12-19 09:24:44
○ 2026-03-25 05:58:36

○NSdns3.name-services.com2015-12-19 → 2015-12-19 · 4 obs

○ 2015-08-17 15:43:54
● 2015-12-19 09:24:44
○ 2016-03-25 02:23:38
○ 2026-03-25 05:58:36

○NSdns4.name-services.com2015-12-19 → 2015-12-19 · 4 obs

○ 2015-08-17 15:43:54
● 2015-12-19 09:24:44
○ 2016-03-25 02:23:38
○ 2026-03-25 05:58:36

○NSdns5.name-services.com2015-12-19 → 2015-12-19 · 4 obs

○ 2015-08-17 15:43:54
● 2015-12-19 09:24:44
○ 2016-03-25 02:23:38
○ 2026-03-25 05:58:36

●NSns1.trafficmonarch.com2026-03-21 → 2026-03-25 · 3 obs

○ 2017-12-31 00:17:28
● 2026-03-21 20:20:48
● 2026-03-25 05:58:36

●NSns2.trafficmonarch.com2026-03-21 → 2026-03-25 · 3 obs

○ 2017-12-31 00:17:28
● 2026-03-21 20:20:48
● 2026-03-25 05:58:36

●MXmail.trafficmonarch.com2016-03-25 → 2026-03-25 · 6 obs

○ 2015-12-19 09:24:44
● 2016-03-25 02:23:38
● 2016-09-08 05:54:18
○ 2017-12-31 00:17:28
● 2026-03-21 20:20:48
● 2026-03-25 05:58:36

○MXmx1.emailsrvr.com2015-08-17 → 2015-08-17 · 3 obs

● 2015-08-17 15:43:54
○ 2015-12-19 09:24:44
○ 2026-03-25 05:58:36

○MXmx2.emailsrvr.com2015-08-17 → 2015-08-17 · 3 obs

● 2015-08-17 15:43:54
○ 2015-12-19 09:24:44
○ 2026-03-25 05:58:36

○MXp.nsm.ctmail.com2015-12-19 → 2015-12-19 · 4 obs

○ 2015-08-17 15:43:54
● 2015-12-19 09:24:44
○ 2016-03-25 02:23:38
○ 2026-03-25 05:58:36

○A198.54.115.1722016-09-08 → 2016-09-08 · 4 obs

○ 2016-03-25 02:23:38
● 2016-09-08 05:54:18
○ 2017-12-31 00:17:28
○ 2026-03-25 05:58:36

○A199.188.204.1432016-03-25 → 2016-03-25 · 4 obs

○ 2015-12-19 09:24:44
● 2016-03-25 02:23:38
○ 2016-09-08 05:54:18
○ 2026-03-25 05:58:36

●A203.161.33.682026-03-21 → 2026-03-25 · 3 obs

○ 2017-12-31 00:17:28
● 2026-03-21 20:20:48
● 2026-03-25 05:58:36

○A64.74.223.302015-12-19 → 2015-12-19 · 4 obs

○ 2015-08-17 15:43:54
● 2015-12-19 09:24:44
○ 2016-03-25 02:23:38
○ 2026-03-25 05:58:36

○A98.129.229.2152015-08-17 → 2015-08-17 · 3 obs

● 2015-08-17 15:43:54
○ 2015-12-19 09:24:44
○ 2026-03-25 05:58:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net...	-
trafficmonarch.com	ns1.trafficmonarch.com, ns2.trafficmonarch.com	2 records

✅ Authoritative Response

Server:203.161.33.68

NS records: ns1.trafficmonarch.com, ns2.trafficmonarch.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for trafficmonarch.com (unsigned zone)

⏱️ Timing

Total: 218ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`203.161.33.68`
NS	2	`ns1.trafficmonarch.com, ns2.trafficmonarch.com`
MX	1	`mail.trafficmonarch.com (pri: 5)`
TXT	1	`v=spf1 ip4:203.161.33.68 +a +mx +ip4:162`
SOA	1	`ns1.trafficmonarch.com hosting-notificat`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.trafficmonarch.com, ns2.trafficmonarch.com)

Analysis

Hierarchy

trafficmonarch.com is a parent of ns2.trafficmonarch.com, ns1.trafficmonarch.com and mail.trafficmonarch.com.

IP Addresses

trafficmonarch.com points to a single IP number: 203.161.33.68.

Other host names, for instance rollmetrix.com, mail.trafficmonarch.com, cdnjet.io, ns2.trafficmonarch.com and trafficsyncpro.com share IP numbers with trafficmonarch.com.

Name Servers

Delegation for trafficmonarch.com rests with two name servers, ns1.trafficmonarch.com and ns2.trafficmonarch.com.

The name server setup used by trafficmonarch.com is shared with other domains such as (0x616e616c)yticharbor.com and cdnjet.io and trafficsyncpro.com.

Host names sharing a single IP:

ns1.trafficmonarch.com points to 203.161.33.68

ns2.trafficmonarch.com points to 203.161.33.68

Host names that point to 203.161.33.68: ns1.trafficmonarch.com and ns2.trafficmonarch.com

Mail Servers

trafficmonarch.com is handled by a single mail server, mail.trafficmonarch.com.

mail.trafficmonarch.com points to a single IP: 203.161.33.68.

trafficmonarch.com - robtex.com