whatwouldthealgorithmdo.com - dns.ninja
whatwouldthealgorithmdo.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=1782551295 | ||||||
Same first word
whatwouldthealgorithmdo.com |
DNS History
8 records (8 active, 0 former)
●NSns-cloud-b1.googledomains.com2026-04-06 → 2026-06-27 · 2 obs
● 2026-06-27 09:21:32
●NSns-cloud-b2.googledomains.com2026-04-06 → 2026-06-27 · 2 obs
● 2026-06-27 09:21:32
●NSns-cloud-b3.googledomains.com2026-04-06 → 2026-06-27 · 2 obs
● 2026-06-27 09:21:32
●NSns-cloud-b4.googledomains.com2026-04-06 → 2026-06-27 · 2 obs
● 2026-06-27 09:21:32
●A198.185.159.1442026-04-06 → 2026-06-27 · 2 obs
● 2026-06-27 09:21:32
●A198.185.159.1452026-04-06 → 2026-06-27 · 2 obs
● 2026-06-27 09:21:32
●A198.49.23.1442026-04-06 → 2026-06-27 · 2 obs
● 2026-06-27 09:21:32
●A198.49.23.1452026-04-06 → 2026-06-27 · 2 obs
● 2026-06-27 09:21:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net, e.gtld-servers.net... | - |
| whatwouldthealgorithmdo.com | ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.38.107
NS records: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for whatwouldthealgorithmdo.com (unsigned zone)
⏱️ Timing
Total: 455ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 198.49.23.145, 198.185.159.145... |
| NS | 4 | ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com... |
| SOA | 1 | ns-cloud-b1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-b1.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com...)
Analysis
IP Addresses
whatwouldthealgorithmdo.com points to the four IP addresses 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
Additional host names — jayleegrooves.com, acbcs.org, thewreathbarn.com and two others — share IP numbers with whatwouldthealgorithmdo.com.
Name Servers
whatwouldthealgorithmdo.com has four authoritative name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.
The name servers of whatwouldthealgorithmdo.com overlap at least partially with those of other domains — among them wisdomweaver.org, ashonair.com, slesha.com and two more.
Each of the four hosts ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com has two IP addresses. ns-cloud-b1.googledomains.com points to 216.239.32.107 and 2001:4860:4802:32::6b. ns-cloud-b2.googledomains.com points to 216.239.34.107 and 2001:4860:4802:34::6b. ns-cloud-b3.googledomains.com points to 216.239.36.107 and 2001:4860:4802:36::6b. ns-cloud-b4.googledomains.com points to 216.239.38.107 and 2001:4860:4802:38::6b.