`containerpartner.no`

DNSSEC	🔒 Signed (DS record present)
A	2a01:5b40:0:248::52^{🇳🇴 DOMENESHOP2a01:5b40::/48}
A	194.63.248.52^{🇳🇴 DOMENESHOP194.63.248.0/24}
NS	`ns1.hyp.net` ⭐
		A	2a01:5b40:ac1::1^{🇳🇴 DOMENESHOP2a01:5b40:ac1::/48}
			PTR	`ns1.hyp.net`
		A	151.249.124.1^{🇳🇴 DOMENESHOP151.249.124.0/24}
			PTR	`ns1.hyp.net`
NS	`ns2.hyp.net`
		A	2001:67c:1bc::10^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns2.hyp.net`
		A	192.174.68.10^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns2.hyp.net`
NS	`ns3.hyp.net`
		A	2a01:5b40:ac3::1^{🇳🇴 GRUNERNETT2a01:5b40:ac3::/48 DOMENESHOP}
			PTR	`ns3.hyp.net`
SOA	`ns1.hyp.net`hostmaster@domeneshop.no serial=1776869806

`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-04-24 #16

Previously NS for

containerpartner.no

Same first word

containerpartner.no

DNS History

9 records (5 active, 4 former)

○NSa.ns.containerpartner.no2015-11-15 → 2018-09-18 · 4 obs

● 2015-11-15 00:25:16
● 2018-09-18 20:26:06
○ 2026-02-17 07:00:26
○ 2026-04-24 05:31:20

○NSb.ns.containerpartner.no2015-11-15 → 2017-02-14 · 4 obs

● 2015-11-15 00:25:16
● 2017-02-14 00:59:18
○ 2018-09-18 20:26:06
○ 2026-04-24 05:31:20

○NScontainerpartner.no2015-11-15 → 2018-09-18 · 4 obs

● 2015-11-15 00:25:16
● 2018-09-18 20:26:06
○ 2026-02-17 07:00:26
○ 2026-04-24 05:31:20

●NSns1.hyp.net2026-02-17 → 2026-04-24 · 3 obs

○ 2018-09-18 20:26:06
● 2026-02-17 07:00:26
● 2026-04-24 05:31:20

●NSns2.hyp.net2026-02-17 → 2026-04-24 · 3 obs

○ 2018-09-18 20:26:06
● 2026-02-17 07:00:26
● 2026-04-24 05:31:20

●NSns3.hyp.net2026-02-17 → 2026-04-24 · 3 obs

○ 2018-09-18 20:26:06
● 2026-02-17 07:00:26
● 2026-04-24 05:31:20

○A178.236.66.552015-11-15 → 2018-09-18 · 4 obs

● 2015-11-15 00:25:16
● 2018-09-18 20:26:06
○ 2026-02-17 07:00:26
○ 2026-04-24 05:31:20

●A194.63.248.522026-02-17 → 2026-04-24 · 3 obs

○ 2018-09-18 20:26:06
● 2026-02-17 07:00:26
● 2026-04-24 05:31:20

●A2a01:5b40:0:248::522026-02-17 → 2026-04-24 · 3 obs

○ 2018-09-18 20:26:06
● 2026-02-17 07:00:26
● 2026-04-24 05:31:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
no	i.nic.no, x.nic.no, y.nic.no, z.nic.no...	-
containerpartner.no	ns3.hyp.net, ns2.hyp.net, ns1.hyp.net	-

✅ Authoritative Response

Server:192.174.68.10

NS records: ns3.hyp.net, ns2.hyp.net, ns1.hyp.net

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 1277ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`194.63.248.52`
AAAA	1	`2a01:5b40:0:248::52`
NS	3	`ns3.hyp.net, ns1.hyp.net...`
SOA	1	`ns1.hyp.net hostmaster.domeneshop.no`

Analysis

IP Addresses

containerpartner.no points to two IP numbers: 2a01:5b40:0:248::52 and 194.63.248.52.

Other host names such as nssf.no, wonderland.no, stylizimo.com, entelios.se and erlend.com share IPs with containerpartner.no.

Name Servers

containerpartner.no is delegated to three name servers: ns1.hyp.net, ns2.hyp.net and ns3.hyp.net.

containerpartner.no at least partially shares name servers with other domains, for example ttp.no, langholm.no, blaafladt.net, abmatter.com and modellnorge.no.

Host names with two IPs:

ns1.hyp.net points to 2a01:5b40:ac1::1 and 151.249.124.1.

ns2.hyp.net points to 2001:67c:1bc::10 and 192.174.68.10.

Host names with one IP:

ns3.hyp.net points to 2a01:5b40:ac3::1.

containerpartner.no - robtex.com