directcpu.com - dns.ninja

`directcpu.com`

DNSSEC	⚠️ Not signed
NS	`ns1.namebrightdns.com` ⭐
		A	2600:1f18:683a:ae1a:6900:d1bd:7672:d0ca^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1a:7bc2:638d:8ca6:fcc4^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:d57d:390a:64b4:d4f1^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	52.203.211.134^{🇺🇸 Amazon52.200.0.0/13 EC2 IAD prefix}
			PTR	`ec2-52-203-211-134.compute-1.amazonaws.com`
		A	52.204.81.90^{🇺🇸 Amazon52.200.0.0/13 EC2 IAD prefix}
			PTR	`ec2-52-204-81-90.compute-1.amazonaws.com`
NS	`ns2.namebrightdns.com`
		A	2600:1f18:683a:ae1b:885d:9b52:c623:6fb9^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	54.234.117.29^{🇺🇸 Amazon54.234.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-234-117-29.compute-1.amazonaws.com`
		A	54.243.19.140^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-243-19-140.compute-1.amazonaws.com`
SOA	`ns1.namebrightdns.com`dns@namebright.com 2026-07-11 #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=1783768122

Same first word

directcpu.biz

directcpu.com

Similar names

DNS History

19 records (2 active, 17 former)

○NSns1.dn(0x736578)it.com2008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 22:13:38
○ 2015-06-30 11:52:00
○ 2026-07-11 11:33:40

●NSns1.namebrightdns.com2026-03-21 → 2026-07-11 · 3 obs

○ 2020-02-03 05:36:40
● 2026-03-21 21:51:38
● 2026-07-11 11:33:40

○NSns1626.ztomy.com2017-02-10 → 2017-02-10 · 4 obs

○ 2016-04-30 08:54:52
● 2017-02-10 22:39:36
○ 2020-02-03 05:36:40
○ 2026-07-11 11:33:40

○NSns1646.ztomy.com2015-06-30 → 2016-04-30 · 5 obs

○ 2008-03-11 22:13:38
● 2015-06-30 11:52:00
● 2016-04-30 08:54:52
○ 2017-02-10 22:39:36
○ 2026-07-11 11:33:40

○NSns2.dn(0x736578)it.com2008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 22:13:38
○ 2015-06-30 11:52:00
○ 2026-07-11 11:33:40

●NSns2.namebrightdns.com2026-03-21 → 2026-07-11 · 3 obs

○ 2020-02-03 05:36:40
● 2026-03-21 21:51:38
● 2026-07-11 11:33:40

○NSns2626.ztomy.com2017-02-10 → 2017-02-10 · 4 obs

○ 2016-04-30 08:54:52
● 2017-02-10 22:39:36
○ 2020-02-03 05:36:40
○ 2026-07-11 11:33:40

○NSns2646.ztomy.com2015-06-30 → 2016-04-30 · 5 obs

○ 2008-03-11 22:13:38
● 2015-06-30 11:52:00
● 2016-04-30 08:54:52
○ 2017-02-10 22:39:36
○ 2026-07-11 11:33:40

○NSnsg1.namebrightdns.com2020-02-03 → 2020-02-03 · 4 obs

○ 2017-02-10 22:39:36
● 2020-02-03 05:36:40
○ 2026-03-21 21:51:38
○ 2026-07-11 11:33:40

○NSnsg2.namebrightdns.com2020-02-03 → 2020-02-03 · 4 obs

○ 2017-02-10 22:39:36
● 2020-02-03 05:36:40
○ 2026-03-21 21:51:38
○ 2026-07-11 11:33:40

○MXalt1.aspmx.l.google.com2008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 22:13:38
○ 2015-06-30 11:52:00
○ 2026-07-11 11:33:40

○MXalt2.aspmx.l.google.com2008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 22:13:38
○ 2015-06-30 11:52:00
○ 2026-07-11 11:33:40

○MXaspmx.l.google.com2008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 22:13:38
○ 2015-06-30 11:52:00
○ 2026-07-11 11:33:40

○MXaspmx2.googlemail.com2008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 22:13:38
○ 2015-06-30 11:52:00
○ 2026-07-11 11:33:40

○A141.8.226.142015-06-30 → 2016-04-30 · 5 obs

○ 2008-03-11 22:13:38
● 2015-06-30 11:52:00
● 2016-04-30 08:54:52
○ 2017-02-10 22:39:36
○ 2026-07-11 11:33:40

○A204.11.56.482017-02-10 → 2017-02-10 · 4 obs

○ 2016-04-30 08:54:52
● 2017-02-10 22:39:36
○ 2020-02-03 05:36:40
○ 2026-07-11 11:33:40

○A66.177.85.1892008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 22:13:38
○ 2015-06-30 11:52:00
○ 2026-07-11 11:33:40

○CNAMEhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com2020-02-03 → 2020-02-03 · 3 obs

● 2020-02-03 05:36:40
○ 2026-03-21 21:51:38
○ 2026-07-11 11:33:40

○PTRns1626.ztomy.com2017-02-10 → 2017-02-10 · 3 obs

● 2017-02-10 22:39:36
○ 2026-03-21 21:51:38
○ 2026-07-11 11:33:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
directcpu.com	ns1.namebrightdns.com, ns2.namebrightdns.com	8 records

✅ Authoritative Response

Server:52.203.211.134

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for directcpu.com (unsigned zone)

⏱️ Timing

Total: 262ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.namebrightdns.com, ns2.namebrightdns.com`
SOA	1	`ns1.namebrightdns.com dns.namebright.com`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.namebrightdns.com, ns1.namebrightdns.com, ns1.namebrightdns.com...)

Analysis

Name Servers

directcpu.com has two authoritative name servers — ns1.namebrightdns.com and ns2.namebrightdns.com.

directcpu.com shares its NS records with other domains, for example www.adriahotels.com, leadpm.cn--ww.analysiswebsites.com, vaqf.com and two others.

There is at least partial name server overlap between directcpu.com and other domains — gistler.com, nappyland.com, thatengine.com and two more among them.

These name servers tend to appear in combination with the name servers nsg1.namebrightdns.com, nsg2.namebrightdns.com, domain-for-sale.hugedomainsdns.com and forsale.hugedomainsdns.com.

Host names directing to five IP addresses:

ns1.namebrightdns.com has four IP addresses — 52.203.211.134, 52.204.81.90, 2600:1f18:683a:ae1a:6900:d1bd:7672:d0ca and two others.

Hostnames that map to three IP numbers:

ns2.namebrightdns.com resolves to 54.234.117.29, 54.243.19.140 and 2600:1f18:683a:ae1b:885d:9b52:c623:6fb9.