adminweb.no - dns.ninja

`adminweb.no`

DNSSEC	⚠️ Not signed
A	18.208.88.157^{🇺🇸 Amazon18.208.0.0/13 EC2 IAD prefix}
		PTR	`ec2-18-208-88-157.compute-1.amazonaws.com`
A	98.84.224.111^{🇺🇸 Amazon98.80.0.0/13 EC2 IAD Prefix}
NS	`dns1.p01.nsone.net` ⭐
		A	2620:4d:4000:6259:7:1:0:1^{🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48}
			PTR	`dns1.p01.nsone.net`
		A	198.51.44.1^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			PTR	`dns1.p01.nsone.net`
NS	`dns2.p01.nsone.net`
		A	2a00:edc0:6259:7:1::2^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns2.p01.nsone.net`
		A	198.51.45.1^{🇺🇸 NSONE198.51.45.0/24 198.51.45.0}
			PTR	`dns2.p01.nsone.net`
NS	`dns3.p01.nsone.net`
		A	2620:4d:4000:6259:7:1:0:3^{🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48}
			PTR	`dns3.p01.nsone.net`
		A	198.51.44.65^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			PTR	`dns3.p01.nsone.net`
NS	`dns4.p01.nsone.net`
		A	2a00:edc0:6259:7:1::4^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns4.p01.nsone.net`
		A	198.51.45.65^{🇺🇸 NSONE198.51.45.0/24 198.51.45.0}
			PTR	`dns4.p01.nsone.net`
SOA	`dns1.p01.nsone.net`domains+netlify@netlify.com serial=1680186019

`no`

	DNSSEC	🔒 Signed (DS record present)
	NS	`charm.norid.no` ⭐
	NS	`i.nic.no`
	NS	`njet.norid.no`
	NS	`not.norid.no`
	NS	`x.nic.no`
	NS	`y.nic.no`
	NS	`z.nic.no`
	SOA	`charm.norid.no`hostmaster@norid.no 2026-07-21 #81

Same first word

adminweb.jp.net

adminweb.mx

adminweb.ir

adminweb.ch

adminweb.nl

adminweb.es

adminweb.co

adminweb.no

adminweb.org

adminweb.ru

adminweb.de

adminweb.ro

adminweb.eu

adminweb.net

adminweb.jp

adminweb.com

adminweb.com.br

adminweb.at

Similar names

DNS History

17 records (6 active, 11 former)

●NSdns1.p01.nsone.net2026-03-30 → 2026-07-21 · 3 obs

○ 2017-04-19 01:43:34
● 2026-03-30 09:33:14
● 2026-07-21 23:22:28

●NSdns2.p01.nsone.net2026-03-30 → 2026-07-21 · 3 obs

○ 2017-04-19 01:43:34
● 2026-03-30 09:33:14
● 2026-07-21 23:22:28

●NSdns3.p01.nsone.net2026-03-30 → 2026-07-21 · 3 obs

○ 2017-04-19 01:43:34
● 2026-03-30 09:33:14
● 2026-07-21 23:22:28

●NSdns4.p01.nsone.net2026-03-30 → 2026-07-21 · 3 obs

○ 2017-04-19 01:43:34
● 2026-03-30 09:33:14
● 2026-07-21 23:22:28

○NSns1.hyp.net2015-08-18 → 2017-04-19 · 4 obs

● 2015-08-18 05:36:50
● 2017-04-19 01:43:34
○ 2026-03-30 09:33:14
○ 2026-07-21 23:22:28

○NSns2.hyp.net2015-08-18 → 2017-04-19 · 4 obs

● 2015-08-18 05:36:50
● 2017-04-19 01:43:34
○ 2026-03-30 09:33:14
○ 2026-07-21 23:22:28

○NSns3.hyp.net2015-08-18 → 2017-04-19 · 4 obs

● 2015-08-18 05:36:50
● 2017-04-19 01:43:34
○ 2026-03-30 09:33:14
○ 2026-07-21 23:22:28

○MXalt1.aspmx.l.google.com2015-08-18 → 2017-04-19 · 4 obs

● 2015-08-18 05:36:50
● 2017-04-19 01:43:34
○ 2026-03-30 09:33:14
○ 2026-07-21 23:22:28

○MXalt2.aspmx.l.google.com2015-08-18 → 2017-04-19 · 4 obs

● 2015-08-18 05:36:50
● 2017-04-19 01:43:34
○ 2026-03-30 09:33:14
○ 2026-07-21 23:22:28

○MXaspmx.l.google.com2015-08-18 → 2017-04-19 · 4 obs

● 2015-08-18 05:36:50
● 2017-04-19 01:43:34
○ 2026-03-30 09:33:14
○ 2026-07-21 23:22:28

○MXaspmx2.googlemail.com2015-08-18 → 2017-04-19 · 4 obs

● 2015-08-18 05:36:50
● 2017-04-19 01:43:34
○ 2026-03-30 09:33:14
○ 2026-07-21 23:22:28

○MXaspmx3.googlemail.com2015-08-18 → 2017-04-19 · 4 obs

● 2015-08-18 05:36:50
● 2017-04-19 01:43:34
○ 2026-03-30 09:33:14
○ 2026-07-21 23:22:28

●A18.208.88.1572026-03-30 → 2026-07-21 · 6 obs

○ 2017-04-19 01:43:34
● 2026-03-30 09:33:14
● 2026-05-06 20:49:24
○ 2026-05-07 09:52:08
● 2026-06-04 08:06:42
● 2026-07-21 23:22:28

○A35.157.26.1352026-05-07 → 2026-05-07 · 4 obs

○ 2026-05-06 20:49:24
● 2026-05-07 09:52:08
○ 2026-06-04 08:06:42
○ 2026-07-21 23:22:28

○A46.38.179.1382015-08-18 → 2017-04-19 · 4 obs

● 2015-08-18 05:36:50
● 2017-04-19 01:43:34
○ 2026-03-30 09:33:14
○ 2026-07-21 23:22:28

○A63.176.8.2182026-05-07 → 2026-05-07 · 4 obs

○ 2026-05-06 20:49:24
● 2026-05-07 09:52:08
○ 2026-06-04 08:06:42
○ 2026-07-21 23:22:28

●A98.84.224.1112026-03-30 → 2026-07-21 · 6 obs

○ 2017-04-19 01:43:34
● 2026-03-30 09:33:14
● 2026-05-06 20:49:24
○ 2026-05-07 09:52:08
● 2026-06-04 08:06:42
● 2026-07-21 23:22:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
no	y.nic.no, z.nic.no, i.nic.no, njet.norid.no...	-
adminweb.no	dns3.p01.nsone.net, dns4.p01.nsone.net, dns1.p01.nsone.net, dns2.p01.nsone.net	-

✅ Authoritative Response

Server:198.51.44.65

NS records: dns3.p01.nsone.net, dns4.p01.nsone.net, dns1.p01.nsone.net, dns2.p01.nsone.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for adminweb.no (unsigned zone)

⏱️ Timing

Total: 1376ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`98.84.224.111, 18.208.88.157`
NS	4	`dns3.p01.nsone.net, dns2.p01.nsone.net...`
SOA	1	`dns1.p01.nsone.net domains+netlify.netli`

Analysis

IP Addresses

adminweb.no has two IP addresses: 18.208.88.157 and 98.84.224.111

ct.app, fif.li, dumels.com plus two other host names have IP numbers in common with adminweb.no.

Name Servers

Four name servers handle the delegation for adminweb.no: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net and dns4.p01.nsone.net.

There is at least partial name server overlap between adminweb.no and other domains — dragoncityadventures.com, foothills-ranch.com, bloombergbusinessweekdesign.com and two more among them.

These name servers regularly appear alongside ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com and 7 other name servers in NS record sets.

All four hostnames — dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net and dns4.p01.nsone.net — resolve to two IP numbers apiece: dns1.p01.nsone.net to 198.51.44.1 and 2620:4d:4000:6259:7:1:0:1; dns2.p01.nsone.net to 198.51.45.1 and 2a00:edc0:6259:7:1::2; dns3.p01.nsone.net to 198.51.44.65 and 2620:4d:4000:6259:7:1:0:3; dns4.p01.nsone.net to 198.51.45.65 and 2a00:edc0:6259:7:1::4.