`teamrelocations.no`

DNSSEC	⚠️ Not signed
A	135.181.53.2^{🇫🇮 Hetzner135.181.0.0/16 HETZNER-DC}
		PTR	`ns.kamy.no`
NS	`ns1-06.azure-dns.com` ⭐
		A	2603:1061:0:700::6^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-06.azure-dns.com`
		A	13.107.236.6^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-06.azure-dns.com`
NS	`ns2-06.azure-dns.net`
		A	2620:1ec:8ec:700::6^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-06.azure-dns.net`
		A	150.171.21.6^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-06.azure-dns.net`
NS	`ns3-06.azure-dns.org`
		A	2a01:111:4000:700::6^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-06.azure-dns.org`
		A	204.14.183.6^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-06.azure-dns.org`
NS	`ns4-06.azure-dns.info`
		A	2620:1ec:bda:700::6^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-06.azure-dns.info`
		A	208.84.5.6^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-06.azure-dns.info`
MX	`web4.kamy.no` ⭐
TXT	`v=spf1 ip4:138.201.240.199 ip4:94.130.158.201 ip4:159.69.140.29 -all`
SOA	`ns1-06.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

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

Same first word

teamrelocations.com

teamrelocations.no

DNS History

19 records (6 active, 13 former)

○NSkurt.ns.cloudflare.com2020-03-13 → 2020-03-13 · 4 obs

○ 2017-04-08 15:34:54
● 2020-03-13 01:32:58
○ 2026-02-22 12:02:10
○ 2026-03-23 17:30:20

○NSns.kamy.no2017-04-08 → 2017-04-08 · 4 obs

○ 2016-08-07 20:55:08
● 2017-04-08 15:34:54
○ 2020-03-13 01:32:58
○ 2026-03-23 17:30:20

○NSns01.one.com2015-05-23 → 2016-08-07 · 4 obs

● 2015-05-23 11:02:40
● 2016-08-07 20:55:08
○ 2017-04-08 15:34:54
○ 2026-03-23 17:30:20

○NSns02.one.com2015-05-23 → 2016-08-07 · 4 obs

● 2015-05-23 11:02:40
● 2016-08-07 20:55:08
○ 2017-04-08 15:34:54
○ 2026-03-23 17:30:20

●NSns1-06.azure-dns.com2026-02-22 → 2026-03-23 · 3 obs

○ 2020-03-13 01:32:58
● 2026-02-22 12:02:10
● 2026-03-23 17:30:20

●NSns2-06.azure-dns.net2026-02-22 → 2026-03-23 · 3 obs

○ 2020-03-13 01:32:58
● 2026-02-22 12:02:10
● 2026-03-23 17:30:20

○NSns2.kamy.no2017-04-08 → 2017-04-08 · 4 obs

○ 2016-08-07 20:55:08
● 2017-04-08 15:34:54
○ 2020-03-13 01:32:58
○ 2026-03-23 17:30:20

●NSns3-06.azure-dns.org2026-02-22 → 2026-03-23 · 3 obs

○ 2020-03-13 01:32:58
● 2026-02-22 12:02:10
● 2026-03-23 17:30:20

●NSns4-06.azure-dns.info2026-02-22 → 2026-03-23 · 3 obs

○ 2020-03-13 01:32:58
● 2026-02-22 12:02:10
● 2026-03-23 17:30:20

○NSpat.ns.cloudflare.com2020-03-13 → 2020-03-13 · 4 obs

○ 2017-04-08 15:34:54
● 2020-03-13 01:32:58
○ 2026-02-22 12:02:10
○ 2026-03-23 17:30:20

○MXmxcluster1.one.com2015-05-23 → 2016-08-07 · 4 obs

● 2015-05-23 11:02:40
● 2016-08-07 20:55:08
○ 2017-04-08 15:34:54
○ 2026-03-23 17:30:20

○MXmxcluster2.one.com2015-05-23 → 2016-08-07 · 4 obs

● 2015-05-23 11:02:40
● 2016-08-07 20:55:08
○ 2017-04-08 15:34:54
○ 2026-03-23 17:30:20

○MXweb.kamy.no2017-04-08 → 2017-04-08 · 4 obs

○ 2016-08-07 20:55:08
● 2017-04-08 15:34:54
○ 2020-03-13 01:32:58
○ 2026-03-23 17:30:20

●MXweb4.kamy.no2020-03-13 → 2026-03-23 · 3 obs

○ 2017-04-08 15:34:54
● 2020-03-13 01:32:58
● 2026-03-23 17:30:20

○A104.27.136.412020-03-13 → 2020-03-13 · 4 obs

○ 2017-04-08 15:34:54
● 2020-03-13 01:32:58
○ 2026-02-22 12:02:10
○ 2026-03-23 17:30:20

○A104.27.137.412020-03-13 → 2020-03-13 · 4 obs

○ 2017-04-08 15:34:54
● 2020-03-13 01:32:58
○ 2026-02-22 12:02:10
○ 2026-03-23 17:30:20

●A135.181.53.22026-02-22 → 2026-03-23 · 3 obs

○ 2020-03-13 01:32:58
● 2026-02-22 12:02:10
● 2026-03-23 17:30:20

○A144.76.249.2362017-04-08 → 2017-04-08 · 4 obs

○ 2016-08-07 20:55:08
● 2017-04-08 15:34:54
○ 2020-03-13 01:32:58
○ 2026-03-23 17:30:20

○A46.30.211.322015-05-23 → 2016-08-07 · 4 obs

● 2015-05-23 11:02:40
● 2016-08-07 20:55:08
○ 2017-04-08 15:34:54
○ 2026-03-23 17:30:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
no	i.nic.no, x.nic.no, y.nic.no, z.nic.no...	11 records
teamrelocations.no	ns3-06.azure-dns.org, ns4-06.azure-dns.info, ns1-06.azure-dns.com, ns2-06.azure-dns.net	-

✅ Authoritative Response

Server:208.84.5.6

NS records: ns3-06.azure-dns.org, ns4-06.azure-dns.info, ns1-06.azure-dns.com, ns2-06.azure-dns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for teamrelocations.no (unsigned zone)

⏱️ Timing

Total: 757ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`135.181.53.2`
NS	4	`ns1-06.azure-dns.com, ns2-06.azure-dns.net...`
MX	1	`web4.kamy.no (pri: 0)`
TXT	1	`v=spf1 ip4:138.201.240.199 ip4:94.130.15`
SOA	1	`ns1-06.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 11

In-bailiwick: 11 (i.nic.no, i.nic.no, x.nic.no...)

Analysis

IP Addresses

teamrelocations.no points to a single IP: 135.181.53.2.

Other host names, for instance mail.santaclauspubcrawl.com, mail.himasp.no, www.korpus.no, novanett.no and himasp.no share IP numbers with teamrelocations.no.

Name Servers

teamrelocations.no's delegation is handled by four name servers: ns1-06.azure-dns.com, ns4-06.azure-dns.info, ns2-06.azure-dns.net and ns3-06.azure-dns.org.

teamrelocations.no partially shares name servers with other domains; examples include jaspine.com, ivalolighting.org, consiliumbuildingsafety.no, das-stadtbad.de and xlent.no.

Host names with two IPs:

ns1-06.azure-dns.com points to 2603:1061:0:700::6 and 13.107.236.6

ns4-06.azure-dns.info points to 2620:1ec:bda:700::6 and 208.84.5.6

ns2-06.azure-dns.net points to 2620:1ec:8ec:700::6 and 150.171.21.6

ns3-06.azure-dns.org points to 2a01:111:4000:700::6 and 204.14.183.6

Mail Servers

teamrelocations.no is handled by a single mail server, web4.kamy.no.

teamrelocations.no - robtex.com