0nbase.com - dns.ninja

`0nbase.com`

DNSSEC	⚠️ Not signed
A	52.88.172.89^{🇺🇸 Amazon52.88.0.0/15 EC2 PDX Prefix}
		PTR	`ec2-52-88-172-89.us-west-2.compute.amazonaws.com`
NS	`ns1.markmonitor.com` ⭐
		A	2620:10a:80a8::1^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.1^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns2.markmonitor.com`
		A	2001:67c:10b8::1^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns2.markmonitor.com`
		A	176.97.158.1^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns2.markmonitor.com`
NS	`ns3.markmonitor.com`
		A	2620:10a:80a9::1^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.1^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns4.markmonitor.com`
		A	2001:67c:1bc::1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns1.markmonitor.com`
		A	192.174.68.1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns1.markmonitor.com`
NS	`ns5.markmonitor.com`
		A	2620:10a:80a8::2^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.2^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns6.markmonitor.com`
		A	2001:67c:10b8::3^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns6.markmonitor.com`
		A	176.97.158.3^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns6.markmonitor.com`
NS	`ns7.markmonitor.com`
		A	2620:10a:80a9::2^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.2^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
TXT	`v=spf1 -all`
SOA	`ns1.markmonitor.com`hostmaster@markmonitor.com 2024-04-23 #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=1782932326

Same first word

0nbase.com

DNS History

11 records (8 active, 3 former)

●NSns1.markmonitor.com2026-02-23 → 2026-07-01 · 3 obs

○ 2016-03-20 09:11:06
● 2026-02-23 15:49:02
● 2026-07-01 19:10:16

●NSns2.markmonitor.com2026-02-23 → 2026-07-01 · 3 obs

○ 2016-03-20 09:11:06
● 2026-02-23 15:49:02
● 2026-07-01 19:10:16

●NSns3.markmonitor.com2026-02-23 → 2026-07-01 · 3 obs

○ 2016-03-20 09:11:06
● 2026-02-23 15:49:02
● 2026-07-01 19:10:16

○NSns3.onbase.com2015-12-06 → 2016-03-20 · 4 obs

● 2015-12-06 21:42:56
● 2016-03-20 09:11:06
○ 2026-02-23 15:49:02
○ 2026-07-01 19:10:16

●NSns4.markmonitor.com2026-02-23 → 2026-07-01 · 3 obs

○ 2016-03-20 09:11:06
● 2026-02-23 15:49:02
● 2026-07-01 19:10:16

○NSns4.onbase.com2015-12-06 → 2016-03-20 · 4 obs

● 2015-12-06 21:42:56
● 2016-03-20 09:11:06
○ 2026-02-23 15:49:02
○ 2026-07-01 19:10:16

●NSns5.markmonitor.com2026-02-23 → 2026-07-01 · 3 obs

○ 2016-03-20 09:11:06
● 2026-02-23 15:49:02
● 2026-07-01 19:10:16

●NSns6.markmonitor.com2026-02-23 → 2026-07-01 · 3 obs

○ 2016-03-20 09:11:06
● 2026-02-23 15:49:02
● 2026-07-01 19:10:16

○NSns6.onbase.com2015-12-06 → 2016-03-20 · 4 obs

● 2015-12-06 21:42:56
● 2016-03-20 09:11:06
○ 2026-02-23 15:49:02
○ 2026-07-01 19:10:16

●NSns7.markmonitor.com2026-02-23 → 2026-07-01 · 3 obs

○ 2016-03-20 09:11:06
● 2026-02-23 15:49:02
● 2026-07-01 19:10:16

●A52.88.172.892026-02-23 → 2026-07-01 · 2 obs

● 2026-02-23 15:49:02
● 2026-07-01 19:10:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
0nbase.com	ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com...	14 records

✅ Authoritative Response

Server:149.112.161.1

NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com, ns2.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for 0nbase.com (unsigned zone)

⏱️ Timing

Total: 724ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.88.172.89`
NS	7	`ns1.markmonitor.com, ns2.markmonitor.com...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.markmonitor.com hostmaster.markmonit`

📌 Glue Records Collected

Total: 14

Out-of-bailiwick: 14 (ns1.markmonitor.com, ns1.markmonitor.com, ns3.markmonitor.com...)

Analysis

IP Addresses

0nbase.com directs to one IP number, which is 52.88.172.89.

Among the host names that share IP numbers with 0nbase.com are ppgcares.com, tomfordbeauty.co.il, peoplestylewatch.co.kr and two others.

Name Servers

0nbase.com is served by 7 authoritative name servers — among them ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and 4 others.

0nbase.com shares at least some of its name servers with other domains, including senioren.de, zohocorporation.me, citrixreceiver.com.hk and two others.

These name servers are frequently seen alongside the name servers ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.

Hosts with two IP numbers each:

ns1.markmonitor.com resolves to two addresses: 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com resolves to two addresses: 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com resolves to two addresses: 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com resolves to two addresses: 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com resolves to two addresses: 149.112.160.2 and 2620:10a:80a8::2.

ns6.markmonitor.com resolves to two addresses: 176.97.158.3 and 2001:67c:10b8::3.

ns7.markmonitor.com resolves to two addresses: 149.112.161.2 and 2620:10a:80a9::2.