innerloop.no - dns.ninja

`innerloop.no`

DNSSEC	🔒 Signed (DS record present)
A	2a01:5b40:0:bc03::1^{🇳🇴 DOMENESHOP2a01:5b40::/48}
A	185.134.245.113^{🇳🇴 DOMENESHOP185.134.244.0/22}
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`
		A	151.249.126.3^{🇳🇴 GRUNERNETT151.249.126.0/24 DOMENESHOP}
			PTR	`ns3.hyp.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1f::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f27.1e100.net`
		A	172.253.63.26^{🇺🇸 Google172.253.63.0/24}
			PTR	`bi-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
TXT	`google-site-verification=ET2EA2WSwKawWdYTtQsjodKt1fFIBBo-XPCvQaSm5NY`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns1.hyp.net`hostmaster@domeneshop.no serial=1784724781

`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-08-03 #44

Same first word

innerloop.us

innerloop.com.au

innerloop.fi

innerloop.in

innerloop.it

innerloop.com

innerloop.store

innerloop.biz

innerloop.dk

innerloop.co

innerloop.no

innerloop.net

innerloop.io

innerloop.de

innerloop.org

Similar names

DNS History

16 records (8 active, 8 former)

●NSns1.hyp.net2026-04-03 → 2026-08-03 · 3 obs

○ 2016-05-07 11:05:38
● 2026-04-03 23:22:10
● 2026-08-03 13:28:26

○NSns1.servage.net2015-06-22 → 2016-05-07 · 4 obs

● 2015-06-22 17:47:40
● 2016-05-07 11:05:38
○ 2026-04-03 23:22:10
○ 2026-08-03 13:28:26

●NSns2.hyp.net2026-04-03 → 2026-08-03 · 3 obs

○ 2016-05-07 11:05:38
● 2026-04-03 23:22:10
● 2026-08-03 13:28:26

○NSns2.servage.net2015-06-22 → 2016-05-07 · 4 obs

● 2015-06-22 17:47:40
● 2016-05-07 11:05:38
○ 2026-04-03 23:22:10
○ 2026-08-03 13:28:26

●NSns3.hyp.net2026-04-03 → 2026-08-03 · 3 obs

○ 2016-05-07 11:05:38
● 2026-04-03 23:22:10
● 2026-08-03 13:28:26

○NSns3.servage.net2015-06-22 → 2016-05-07 · 4 obs

● 2015-06-22 17:47:40
● 2016-05-07 11:05:38
○ 2026-04-03 23:22:10
○ 2026-08-03 13:28:26

○NSns4.servage.net2015-06-22 → 2016-05-07 · 4 obs

● 2015-06-22 17:47:40
● 2016-05-07 11:05:38
○ 2026-04-03 23:22:10
○ 2026-08-03 13:28:26

●MXalt1.aspmx.l.google.com2026-04-03 → 2026-08-03 · 3 obs

○ 2016-05-07 11:05:38
● 2026-04-03 23:22:10
● 2026-08-03 13:28:26

●MXalt2.aspmx.l.google.com2026-04-03 → 2026-08-03 · 3 obs

○ 2016-05-07 11:05:38
● 2026-04-03 23:22:10
● 2026-08-03 13:28:26

●MXaspmx.l.google.com2026-04-03 → 2026-08-03 · 3 obs

○ 2016-05-07 11:05:38
● 2026-04-03 23:22:10
● 2026-08-03 13:28:26

○MXmx1.servage.net2015-06-22 → 2016-05-07 · 4 obs

● 2015-06-22 17:47:40
● 2016-05-07 11:05:38
○ 2026-04-03 23:22:10
○ 2026-08-03 13:28:26

○MXmx2.servage.net2015-06-22 → 2016-05-07 · 4 obs

● 2015-06-22 17:47:40
● 2016-05-07 11:05:38
○ 2026-04-03 23:22:10
○ 2026-08-03 13:28:26

●A185.134.245.1132026-04-03 → 2026-08-03 · 3 obs

○ 2016-05-07 11:05:38
● 2026-04-03 23:22:10
● 2026-08-03 13:28:26

○A2a01:3b0:a00:0:db78:cf40::2015-06-22 → 2016-05-07 · 4 obs

● 2015-06-22 17:47:40
● 2016-05-07 11:05:38
○ 2026-04-03 23:22:10
○ 2026-08-03 13:28:26

●A2a01:5b40:0:bc03::12026-04-03 → 2026-08-03 · 3 obs

○ 2016-05-07 11:05:38
● 2026-04-03 23:22:10
● 2026-08-03 13:28:26

○A77.232.66.322015-06-22 → 2016-05-07 · 4 obs

● 2015-06-22 17:47:40
● 2016-05-07 11:05:38
○ 2026-04-03 23:22:10
○ 2026-08-03 13:28:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
no	z.nic.no, njet.norid.no, x.nic.no, not.norid.no...	11 records
innerloop.no	ns2.hyp.net, ns1.hyp.net, ns3.hyp.net	-

✅ Authoritative Response

Server:192.174.68.10

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

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 771ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`185.134.245.113`
AAAA	1	`2a01:5b40:0:bc03::1`
NS	3	`ns3.hyp.net, ns1.hyp.net...`
MX	3	`ASPMX.L.GOOGLE.COM (pri: 1), ALT2.ASPMX.L.GOOGLE.COM (pri: 5)...`
TXT	2	`v=spf1 include:_spf.google.com ~all, google-site-verification=ET2EA2WSwKawWdY`
SOA	1	`ns1.hyp.net hostmaster.domeneshop.no`

📌 Glue Records Collected

Total: 11

In-bailiwick: 11 (z.nic.no, z.nic.no, njet.norid.no...)

Analysis

IP Addresses

innerloop.no resolves to the IP addresses 185.134.245.113 and 2a01:5b40:0:bc03::1

Two other host names, along with bookhovden.com, logicsoccer.com and friluftsbilder.com, also share IP numbers with innerloop.no.

Name Servers

Three name servers are authoritative for innerloop.no: ns1.hyp.net, ns2.hyp.net and ns3.hyp.net.

innerloop.no has at least partial name server overlap with other domains, such as naturopa.info, heksesot.com, ateps.com and two others.

ns1.hyp.net resolves to 151.249.124.1 and 2a01:5b40:ac1::1. ns2.hyp.net resolves to 192.174.68.10 and 2001:67c:1bc::10. ns3.hyp.net resolves to 151.249.126.3 and 2a01:5b40:ac3::1. All three hostnames point to two IP numbers each.

Mail Servers

innerloop.no has three mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.

There is at least a partial MX overlap between innerloop.no and other domains, including jcuv.at, rectoverso.co, homeinsurance-quotes.co.uk and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

aspmx.l.google.com resolves to 172.253.63.26 and 2607:f8b0:4004:c1f::1b. alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1b. alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1b. All three hostnames point to two IP numbers each.