`swatchbijoux.net`

DNSSEC	⚠️ Not signed
NS	`ns1-04.azure-dns.com` ⭐
		A	2603:1061:0:700::4^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
		A	13.107.236.4^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
NS	`ns2-04.azure-dns.net`
		A	2620:1ec:8ec:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
		A	150.171.21.4^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
NS	`ns3-04.azure-dns.org`
		A	2a01:111:4000:700::4^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-04.azure-dns.org`
		A	204.14.183.4^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-04.azure-dns.org`
NS	`ns4-04.azure-dns.info`
		A	2620:1ec:bda:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
		A	208.84.5.4^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
MX	`sgrmgw5.swatchgroup.com` ⭐
		A	149.133.4.180^{🇨🇭 SWISSCOM149.133.4.0/23}
			PTR	`sgrmgw5.swatchgroup.com`
			PTR	`smtp.swatchgroup.com`
MX	`sgrmgw6.swatchgroup.com` ⭐
		A	149.133.4.181^{🇨🇭 SWISSCOM149.133.4.0/23}
			PTR	`sgrmgw6.swatchgroup.com`
			PTR	`smtp.swatchgroup.com`
TXT	`v=spf1 mx -all`
SOA	`ns1-04.azure-dns.com`hostmaster@swatchbijoux.net serial=1750746864

`net`

	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=1778261401

WOT: UNKNOWN (90/100)

Same first word

swatchbijoux.net

swatchbijoux.org

swatchbijoux.info

DNS History

16 records (6 active, 10 former)

●NSns1-04.azure-dns.com2026-05-03 → 2026-05-08 · 3 obs

○ 2017-04-05 13:52:54
● 2026-05-03 12:14:00
● 2026-05-08 17:46:50

○NSns1.swatchgroup.com2015-06-01 → 2017-04-05 · 5 obs

○ 2007-09-19 00:47:42
● 2015-06-01 13:11:24
● 2017-04-05 13:52:54
○ 2026-05-03 12:14:00
○ 2026-05-08 17:46:50

●NSns2-04.azure-dns.net2026-05-03 → 2026-05-08 · 3 obs

○ 2017-04-05 13:52:54
● 2026-05-03 12:14:00
● 2026-05-08 17:46:50

○NSns2.swatchgroup.com2015-06-01 → 2017-04-05 · 5 obs

○ 2007-09-19 00:47:42
● 2015-06-01 13:11:24
● 2017-04-05 13:52:54
○ 2026-05-03 12:14:00
○ 2026-05-08 17:46:50

●NSns3-04.azure-dns.org2026-05-03 → 2026-05-08 · 3 obs

○ 2017-04-05 13:52:54
● 2026-05-03 12:14:00
● 2026-05-08 17:46:50

○NSns3.swatchgroup.com2015-06-01 → 2017-04-05 · 5 obs

○ 2007-09-19 00:47:42
● 2015-06-01 13:11:24
● 2017-04-05 13:52:54
○ 2026-05-03 12:14:00
○ 2026-05-08 17:46:50

●NSns4-04.azure-dns.info2026-05-03 → 2026-05-08 · 3 obs

○ 2017-04-05 13:52:54
● 2026-05-03 12:14:00
● 2026-05-08 17:46:50

○NSns4.swatchgroup.com2015-06-01 → 2017-04-05 · 5 obs

○ 2007-09-19 00:47:42
● 2015-06-01 13:11:24
● 2017-04-05 13:52:54
○ 2026-05-03 12:14:00
○ 2026-05-08 17:46:50

○NSns5.parava.net2007-09-19 → 2007-09-19 · 3 obs

● 2007-09-19 00:47:42
○ 2015-06-01 13:11:24
○ 2026-05-08 17:46:50

○NSns6.parava.net2007-09-19 → 2007-09-19 · 3 obs

● 2007-09-19 00:47:42
○ 2015-06-01 13:11:24
○ 2026-05-08 17:46:50

○MXsgrmgw1.swatchgroup.com2015-06-01 → 2017-04-05 · 5 obs

○ 2007-09-19 00:47:42
● 2015-06-01 13:11:24
● 2017-04-05 13:52:54
○ 2026-05-03 12:14:00
○ 2026-05-08 17:46:50

○MXsgrmgw2.swatchgroup.com2015-06-01 → 2017-04-05 · 5 obs

○ 2007-09-19 00:47:42
● 2015-06-01 13:11:24
● 2017-04-05 13:52:54
○ 2026-05-03 12:14:00
○ 2026-05-08 17:46:50

●MXsgrmgw5.swatchgroup.com2026-05-03 → 2026-05-08 · 3 obs

○ 2017-04-05 13:52:54
● 2026-05-03 12:14:00
● 2026-05-08 17:46:50

●MXsgrmgw6.swatchgroup.com2026-05-03 → 2026-05-08 · 3 obs

○ 2017-04-05 13:52:54
● 2026-05-03 12:14:00
● 2026-05-08 17:46:50

○A193.222.87.1732015-06-01 → 2017-04-05 · 5 obs

○ 2007-09-19 00:47:42
● 2015-06-01 13:11:24
● 2017-04-05 13:52:54
○ 2026-05-03 12:14:00
○ 2026-05-08 17:46:50

○A65.210.194.572007-09-19 → 2007-09-19 · 3 obs

● 2007-09-19 00:47:42
○ 2015-06-01 13:11:24
○ 2026-05-08 17:46:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
swatchbijoux.net	ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info	2 records

✅ Authoritative Response

Server:204.14.183.4

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for swatchbijoux.net (unsigned zone)

⏱️ Timing

Total: 305ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-04.azure-dns.com, ns2-04.azure-dns.net...`
MX	2	`sgrmgw5.swatchgroup.com (pri: 5), sgrmgw6.swatchgroup.com (pri: 5)`
TXT	1	`v=spf1 mx -all`
SOA	1	`ns1-04.azure-dns.com hostmaster.swatchbi`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2-04.azure-dns.net, ns2-04.azure-dns.net)

Analysis

Name Servers

swatchbijoux.net is delegated to four name servers: ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.

swatchbijoux.net at least partially shares name servers with other domains, for instance msdas.org, oticon.qc.ca, uofv.com, clydemarine.com and priex.fr.

Host names with two IP numbers: ns1-04.azure-dns.com points to 2603:1061:0:700::4 and 13.107.236.4; ns4-04.azure-dns.info points to 2620:1ec:bda:700::4 and 208.84.5.4; ns2-04.azure-dns.net points to 2620:1ec:8ec:700::4 and 150.171.21.4; ns3-04.azure-dns.org points to 2a01:111:4000:700::4 and 204.14.183.4.

Mail Servers

swatchbijoux.net is handled by two mail servers: sgrmgw5.swatchgroup.com and sgrmgw6.swatchgroup.com.

The mail server setup for swatchbijoux.net matches that of other domains, for instance longines.online, swatchsite.com, swatchbrasil.com.br, svvatchgroup.net and omegawatche.com.

Host names with a single IP:

sgrmgw5.swatchgroup.com points to 149.133.4.180.

sgrmgw6.swatchgroup.com points to 149.133.4.181.

swatchbijoux.net - robtex.com