`contactcouples.com`

DNSSEC	⚠️ Not signed
A	64.99.64.37^{🇨🇦 TUCOWS64.99.0.0/16 Tucows.com Co}
		PTR	`osrs.systemdns.com`
NS	`ns1.systemdns.com` ⭐
		A	2604:4000:0:d:216:40:47:90^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.systemdns.com`
		A	216.40.47.90^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.systemdns.com`
NS	`ns2.systemdns.com`
		A	2604:4000:2800:d:64:99:148:16^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
		A	64.98.148.16^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.systemdns.com`
NS	`ns3.systemdns.com`
		A	2604:4000:0:d:64:99:96:36^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns3.systemdns.com`
		A	64.99.96.36^{🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2}
			PTR	`ns3.systemdns.com`
SOA	`ns1.systemdns.com`hostmaster@systemdns.com serial=1752594816

`com`

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

Same first word

contactcouples.com

DNS History

7 records (4 active, 3 former)

○NSns1.domainbrandnames.com2015-08-15 → 2017-05-26 · 3 obs

● 2015-08-15 15:51:46
● 2017-05-26 05:21:40
○ 2026-03-24 05:02:18

●NSns1.systemdns.com2026-03-24 → 2026-03-24 · 2 obs

○ 2017-05-26 05:21:40
● 2026-03-24 05:02:18

○NSns2.domainbrandnames.com2015-08-15 → 2017-05-26 · 3 obs

● 2015-08-15 15:51:46
● 2017-05-26 05:21:40
○ 2026-03-24 05:02:18

●NSns2.systemdns.com2026-03-24 → 2026-03-24 · 2 obs

○ 2017-05-26 05:21:40
● 2026-03-24 05:02:18

●NSns3.systemdns.com2026-03-24 → 2026-03-24 · 2 obs

○ 2017-05-26 05:21:40
● 2026-03-24 05:02:18

●A64.99.64.372026-03-24 → 2026-03-24 · 2 obs

○ 2017-05-26 05:21:40
● 2026-03-24 05:02:18

○A75.98.204.1262015-08-15 → 2017-05-26 · 3 obs

● 2015-08-15 15:51:46
● 2017-05-26 05:21:40
○ 2026-03-24 05:02:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
contactcouples.com	ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com	6 records

✅ Authoritative Response

Server:216.40.47.90

NS records: ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for contactcouples.com (unsigned zone)

⏱️ Timing

Total: 187ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`64.99.64.37`
NS	3	`ns3.systemdns.com, ns2.systemdns.com...`
SOA	1	`ns1.systemdns.com hostmaster.systemdns.c`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.systemdns.com, ns1.systemdns.com, ns2.systemdns.com...)

Analysis

IP Addresses

contactcouples.com points to an IP address: 64.99.64.37.

other host names include visteom.com, getfreshsolutions.com, bjmedia.org, webcluster02.cqservices.com and nullmx.www.delights.com; they share IP numbers with contactcouples.com.

Name Servers

contactcouples.com is delegated to three name servers ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com.

contactcouples.com at least partially shares name servers with other domains, for instance gardensbysanders.com, shawscape.info, rscp.co.in, smartfence.net.au and precisionpaintlessdent.com.

Host names with two IP numbers:

ns1.systemdns.com points to 2604:4000:0:d:216:40:47:90 and 216.40.47.90; ns2.systemdns.com points to 2604:4000:2800:d:64:99:148:16 and 64.98.148.16; ns3.systemdns.com points to 2604:4000:0:d:64:99:96:36 and 64.99.96.36.

contactcouples.com - robtex.com