`coulditbevhl.com`

DNSSEC	⚠️ Not signed
NS	`ns-1600.awsdns-08.co.uk` ⭐
		A	2600:9000:5306:4000::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1600.awsdns-08.co.uk`
		A	205.251.198.64^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1600.awsdns-08.co.uk`
NS	`ns-107.awsdns-13.com`
		A	2600:9000:5300:6b00::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-107.awsdns-13.com`
		A	205.251.192.107^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-107.awsdns-13.com`
NS	`ns-1263.awsdns-29.org`
		A	2600:9000:5304:ef00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1263.awsdns-29.org`
		A	205.251.196.239^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1263.awsdns-29.org`
NS	`ns-785.awsdns-34.net`
		A	2600:9000:5303:1100::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-785.awsdns-34.net`
		A	205.251.195.17^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-785.awsdns-34.net`
SOA	`ns-1600.awsdns-08.co.uk`awsdns-hostmaster@amazon.com serial=1

`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=1776108237

Same first word

coulditbevhl.com

coulditbevhl.net

DNS History

4 records (4 active, 0 former)

●NSns-107.awsdns-13.com2026-03-17 → 2026-04-13 · 2 obs

● 2026-03-17 04:39:02
● 2026-04-13 19:32:40

●NSns-1263.awsdns-29.org2026-03-17 → 2026-04-13 · 2 obs

● 2026-03-17 04:39:02
● 2026-04-13 19:32:40

●NSns-1600.awsdns-08.co.uk2026-03-17 → 2026-04-13 · 2 obs

● 2026-03-17 04:39:02
● 2026-04-13 19:32:40

●NSns-785.awsdns-34.net2026-03-17 → 2026-04-13 · 2 obs

● 2026-03-17 04:39:02
● 2026-04-13 19:32:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
coulditbevhl.com	ns-107.awsdns-13.com, ns-785.awsdns-34.net, ns-1600.awsdns-08.co.uk, ns-1263.awsdns-29.org	1 record

✅ Authoritative Response

Server:205.251.192.107

NS records: ns-107.awsdns-13.com, ns-785.awsdns-34.net, ns-1600.awsdns-08.co.uk, ns-1263.awsdns-29.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for coulditbevhl.com (unsigned zone)

⏱️ Timing

Total: 271ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-107.awsdns-13.com, ns-1263.awsdns-29.org...`
SOA	1	`ns-1600.awsdns-08.co.uk awsdns-hostmaste`

📌 Glue Records Collected

Total: 1

Out-of-bailiwick: 1 (ns-107.awsdns-13.com)

Analysis

Name Servers

coulditbevhl.com is delegated to four name servers: ns-107.awsdns-13.com, ns-785.awsdns-34.net, ns-1263.awsdns-29.org and ns-1600.awsdns-08.co.uk.

coulditbevhl.com shares some name servers with other domains, for example cashonline.info, ridepal.com, calabazasvoladoras.com, unlockmorerock.com and d39m1nrlrgpna4.cloudfront.net.

These name servers are often used together with ns-194.awsdns-24.com, ns-692.awsdns-22.net and ns-1269.awsdns-30.org.

Host names with two IP numbers

Two IPs per host:

ns-107.awsdns-13.com points to 2600:9000:5300:6b00::1 and 205.251.192.107

ns-785.awsdns-34.net points to 2600:9000:5303:1100::1 and 205.251.195.17

ns-1263.awsdns-29.org points to 2600:9000:5304:ef00::1 and 205.251.196.239

ns-1600.awsdns-08.co.uk points to 2600:9000:5306:4000::1 and 205.251.198.64

coulditbevhl.com - robtex.com