bitsaver.com - dns.ninja

`bitsaver.com`

DNSSEC	⚠️ Not signed
A	62.72.49.0^{🇩🇪 IIHOS00162.72.48.0/21 HOSTINGER US}
NS	`ns39.domaincontrol.com` ⭐
		A	2603:5:21d1::14^{🇺🇸 GODADDY-DNS2603:5:21d0::/44}
			PTR	`ns39.domaincontrol.com`
		A	97.74.109.20^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns39.domaincontrol.com`
NS	`ns40.domaincontrol.com`
		A	2603:5:22d1::14^{🇺🇸 GODADDY-DNS2603:5:22d0::/44}
			PTR	`ns40.domaincontrol.com`
		A	173.201.77.20^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns40.domaincontrol.com`
MX	`bitsaver-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c931::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr03cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:f802::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:f804::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr05cu00402.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mn2pr02cu00202.inbound.protection.outlook.com`
		A	52.101.9.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mn2pr02cu00202.inbound.protection.outlook.com`
		A	52.101.11.3^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr0501cu00103.inbound.protection.outlook.com`
		A	52.101.41.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01600.inbound.protection.outlook.com`
		A	52.101.194.12^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch0pr04cu00504.inbound.protection.outlook.com`
TXT	`google-site-verification=FheqqgNoGhRoU5UNV8V26qqmwXnl5px5gWPRp6lr6yk`
TXT	`google-site-verification=FydlqwuRbTeeoyVoRA-A1QvTd9UX_uu5tm077nQsmMo`
TXT	`MS=ms18680786`
TXT	`v=spf1 include:secureserver.net -all`
TXT	`google-site-verification=Mj88EsizcEoyb4Ad9olV80pF_NeKWAAwPjCPGOU5B1I`
SOA	`ns39.domaincontrol.com`dns@jomax.net 2024-12-03 #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=1782176570

Same first word

bitsaver.cn

bitsaver.net

bitsaver.com

bitsaver.org

bitsaver.info

Similar names

DNS History

11 records (4 active, 7 former)

○NSns01.cashparking.com2015-06-12 → 2018-10-24 · 4 obs

● 2015-06-12 08:20:14
● 2018-10-24 19:48:26
○ 2026-03-03 15:46:56
○ 2026-06-23 01:11:20

○NSns02.cashparking.com2018-10-24 → 2018-10-24 · 4 obs

○ 2015-06-12 08:20:14
● 2018-10-24 19:48:26
○ 2026-03-03 15:46:56
○ 2026-06-23 01:11:20

●NSns39.domaincontrol.com2026-03-03 → 2026-06-23 · 3 obs

○ 2018-10-24 19:48:26
● 2026-03-03 15:46:56
● 2026-06-23 01:11:20

●NSns40.domaincontrol.com2026-03-03 → 2026-06-23 · 3 obs

○ 2018-10-24 19:48:26
● 2026-03-03 15:46:56
● 2026-06-23 01:11:20

○MX(root)2018-10-24 → 2018-10-24 · 4 obs

○ 2017-02-16 13:28:50
● 2018-10-24 19:48:26
○ 2026-03-03 15:46:56
○ 2026-06-23 01:11:20

○MX102018-10-24 → 2018-10-24 · 4 obs

○ 2017-02-16 13:28:50
● 2018-10-24 19:48:26
○ 2026-03-03 15:46:56
○ 2026-06-23 01:11:20

●MXbitsaver-com.mail.protection.outlook.com2026-03-03 → 2026-06-23 · 3 obs

○ 2018-10-24 19:48:26
● 2026-03-03 15:46:56
● 2026-06-23 01:11:20

○MXmailstore1.secureserver.net2015-06-12 → 2017-02-16 · 4 obs

● 2015-06-12 08:20:14
● 2017-02-16 13:28:50
○ 2018-10-24 19:48:26
○ 2026-06-23 01:11:20

○MXsmtp.secureserver.net2015-06-12 → 2017-02-16 · 4 obs

● 2015-06-12 08:20:14
● 2017-02-16 13:28:50
○ 2018-10-24 19:48:26
○ 2026-06-23 01:11:20

○A184.168.221.962015-06-12 → 2018-10-24 · 4 obs

● 2015-06-12 08:20:14
● 2018-10-24 19:48:26
○ 2026-03-03 15:46:56
○ 2026-06-23 01:11:20

●A62.72.49.02026-03-03 → 2026-06-23 · 3 obs

○ 2018-10-24 19:48:26
● 2026-03-03 15:46:56
● 2026-06-23 01:11:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
bitsaver.com	ns39.domaincontrol.com, ns40.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.109.20

NS records: ns39.domaincontrol.com, ns40.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bitsaver.com (unsigned zone)

⏱️ Timing

Total: 228ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`62.72.49.0`
NS	2	`ns39.domaincontrol.com, ns40.domaincontrol.com`
MX	1	`bitsaver-com.mail.protection.outlook.com`
TXT	5	`google-site-verification=FheqqgNoGhRoU5U, google-site-verification=FydlqwuRbTeeoyV...`
SOA	1	`ns39.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns39.domaincontrol.com, ns39.domaincontrol.com, ns40.domaincontrol.com...)

Analysis

IP Addresses

bitsaver.com directs to one IP number, which is 62.72.49.0.

Among others, nikeshsethmd.com, afoa.us, mail.afoa.us and turfmark.net resolve to the same IP numbers as bitsaver.com.

Name Servers

bitsaver.com uses two name servers for its delegation: ns39.domaincontrol.com and ns40.domaincontrol.com.

bitsaver.com has the same name server delegation as a number of other domains, such as inmateaccess.biz, simplypom.com, withgod.net and two more.

At least some of bitsaver.com's name servers are also used by other domains, among them fxec.net.

The two host names ns39.domaincontrol.com and ns40.domaincontrol.com each have a pair of IP addresses: ns39.domaincontrol.com has 97.74.109.20 and 2603:5:21d1::14, and ns40.domaincontrol.com has 173.201.77.20 and 2603:5:22d1::14.

Mail Servers

bitsaver.com routes its mail through a single mail server, bitsaver-com.mail.protection.outlook.com.

bitsaver-com.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.9.2, 52.101.11.3 and 52.101.41.24, along with 5 other.