`mybasementdigout.com`

DNSSEC	⚠️ Not signed
A	198.54.117.242^{🇺🇸 NAMCHEAP-PH198.54.117.0/24}
NS	`verify-contact-details.namecheap.com` ⭐
		A	198.54.117.252^{🇺🇸 NAMCHEAP-PH198.54.117.0/24}
NS	`failed-whois-verification.namecheap.com`
		A	198.54.117.251^{🇺🇸 NAMCHEAP-PH198.54.117.0/24}
SOA	`verify-contact-details.namecheap.com`support@namecheap.com serial=1775499265

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

⚠️ On DNS blocklist: tif

Previously MX for

mybasementdigout.com

Same first word

mybasementdigout.com

DNS History

10 records (3 active, 7 former)

●NSfailed-whois-verification.namecheap.com2026-04-02 → 2026-04-06 · 3 obs

○ 2017-05-22 17:42:12
● 2026-04-02 10:54:06
● 2026-04-06 18:15:34

○NSns1.justhost.com2015-05-30 → 2017-05-22 · 4 obs

● 2015-05-30 17:53:40
● 2017-05-22 17:42:12
○ 2026-04-02 10:54:06
○ 2026-04-06 18:15:34

○NSns2.justhost.com2015-05-30 → 2017-05-22 · 4 obs

● 2015-05-30 17:53:40
● 2017-05-22 17:42:12
○ 2026-04-02 10:54:06
○ 2026-04-06 18:15:34

●NSverify-contact-details.namecheap.com2026-04-02 → 2026-04-06 · 3 obs

○ 2017-05-22 17:42:12
● 2026-04-02 10:54:06
● 2026-04-06 18:15:34

○MXfallbackmx.spamexperts.eu2017-05-22 → 2017-05-22 · 4 obs

○ 2016-09-21 22:40:56
● 2017-05-22 17:42:12
○ 2026-04-02 10:54:06
○ 2026-04-06 18:15:34

○MXlastmx.spamexperts.net2017-05-22 → 2017-05-22 · 4 obs

○ 2016-09-21 22:40:56
● 2017-05-22 17:42:12
○ 2026-04-02 10:54:06
○ 2026-04-06 18:15:34

○MXmx.spamexperts.com2017-05-22 → 2017-05-22 · 4 obs

○ 2016-09-21 22:40:56
● 2017-05-22 17:42:12
○ 2026-04-02 10:54:06
○ 2026-04-06 18:15:34

○MXmybasementdigout.com2015-05-30 → 2016-09-21 · 4 obs

● 2015-05-30 17:53:40
● 2016-09-21 22:40:56
○ 2017-05-22 17:42:12
○ 2026-04-06 18:15:34

○A173.254.28.132015-05-30 → 2017-05-22 · 4 obs

● 2015-05-30 17:53:40
● 2017-05-22 17:42:12
○ 2026-04-02 10:54:06
○ 2026-04-06 18:15:34

●A198.54.117.2422026-04-02 → 2026-04-06 · 3 obs

○ 2017-05-22 17:42:12
● 2026-04-02 10:54:06
● 2026-04-06 18:15:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
mybasementdigout.com	verify-contact-details.namecheap.com, failed-whois-verification.namecheap.com	2 records

✅ Authoritative Response

Server:198.54.117.252

NS records: verify-contact-details.namecheap.com, failed-whois-verification.namecheap.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mybasementdigout.com (unsigned zone)

⏱️ Timing

Total: 457ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`198.54.117.242`
NS	2	`failed-whois-verification.namecheap.com, verify-contact-details.namecheap.com`
SOA	1	`verify-contact-details.namecheap.com sup`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (verify-contact-details.namecheap.com, failed-whois-verification.namecheap.com)

Analysis

IP Addresses

mybasementdigout.com points to a single IP number: 198.54.117.242.

Other host names, for instance momzsillylife.com, mail.explorar.net, vitabellaevents.com, contentpay.space and auditdocs01.info share IP numbers with mybasementdigout.com.

Name Servers

mybasementdigout.com is delegated to two name servers: failed-whois-verification.namecheap.com and verify-contact-details.namecheap.com.

mybasementdigout.com uses the same name server setup as other domains, for instance mail.arilco.com, alphagerman.com, slxucs.site, young-dxh.info and necraf.boats.

Host names with one IP number:

failed-whois-verification.namecheap.com points to: 198.54.117.251.

verify-contact-details.namecheap.com points to: 198.54.117.252.

mybasementdigout.com - robtex.com