whatcouldbeeco.com - robtex.com
whatcouldbeeco.com
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.netnstld@verisign-grs.com serial=1784202677 | ||||||
Same first word
whatcouldbeeco.com |
DNS History
8 records (8 active, 0 former)
●NSns-cloud-d1.googledomains.com2026-04-05 → 2026-07-16 · 2 obs
● 2026-07-16 12:14:46
●NSns-cloud-d2.googledomains.com2026-04-05 → 2026-07-16 · 2 obs
● 2026-07-16 12:14:46
●NSns-cloud-d3.googledomains.com2026-04-05 → 2026-07-16 · 2 obs
● 2026-07-16 12:14:46
●NSns-cloud-d4.googledomains.com2026-04-05 → 2026-07-16 · 2 obs
● 2026-07-16 12:14:46
●A198.185.159.1442026-04-05 → 2026-07-16 · 2 obs
● 2026-07-16 12:14:46
●A198.185.159.1452026-04-05 → 2026-07-16 · 2 obs
● 2026-07-16 12:14:46
●A198.49.23.1442026-04-05 → 2026-07-16 · 2 obs
● 2026-07-16 12:14:46
●A198.49.23.1452026-04-05 → 2026-07-16 · 2 obs
● 2026-07-16 12:14:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, a.gtld-servers.net, e.gtld-servers.net, c.gtld-servers.net... | - |
| whatcouldbeeco.com | ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.32.109
NS records: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for whatcouldbeeco.com (unsigned zone)
⏱️ Timing
Total: 1856ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 198.185.159.144, 198.49.23.145... |
| NS | 4 | ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com... |
| TXT | 1 | v=spf1 -all |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h2", |
| SOA | 1 | ns-cloud-d1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-d1.googledomains.com, ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com...)
Analysis
IP Addresses
whatcouldbeeco.com points to the four IP addresses 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
biplanefun.com, flura.dk, duenorthtrademark.com and two other host names share IP numbers with whatcouldbeeco.com.
Name Servers
The authoritative name servers for whatcouldbeeco.com are ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com.
At least some of whatcouldbeeco.com's name servers are shared with other domains, for example sakusakumart.com, clockunlimited.com, cowboybootseurope.com and two more.
Four hostnames, each resolving to a pair of IP addresses: ns-cloud-d1.googledomains.com directs to 216.239.32.109 and 2001:4860:4802:32::6d; ns-cloud-d2.googledomains.com directs to 216.239.34.109 and 2001:4860:4802:34::6d; ns-cloud-d3.googledomains.com directs to 216.239.36.109 and 2001:4860:4802:36::6d; ns-cloud-d4.googledomains.com directs to 216.239.38.109 and 2001:4860:4802:38::6d.