whoelseisrunning.com - robtex.com
whoelseisrunning.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=1774365702 | ||||||
Same first word
whoelseisrunning.com |
DNS History
12 records (7 active, 5 former)
●NSns-cloud-a1.googledomains.com2019-03-20 → 2026-03-24 · 2 obs
● 2026-03-24 15:39:48
●NSns-cloud-a2.googledomains.com2019-03-20 → 2026-03-24 · 2 obs
● 2026-03-24 15:39:48
●NSns-cloud-a3.googledomains.com2019-03-20 → 2026-03-24 · 2 obs
● 2026-03-24 15:39:48
●NSns-cloud-a4.googledomains.com2019-03-20 → 2026-03-24 · 2 obs
● 2026-03-24 15:39:48
○A34.242.74.1252026-03-18 → 2026-03-24 · 2 obs
○ 2026-03-24 15:39:48
○A52.18.43.742026-03-18 → 2026-03-18 · 3 obs
● 2026-03-18 12:49:30
○ 2026-03-24 15:39:48
●A52.215.253.682026-03-24 → 2026-03-24 · 2 obs
● 2026-03-24 15:39:48
●A54.220.54.722026-03-18 → 2026-03-24 · 3 obs
● 2026-03-18 12:49:30
● 2026-03-24 15:39:48
○A54.220.83.02026-03-18 → 2026-03-24 · 2 obs
○ 2026-03-24 15:39:48
○A54.247.159.2432026-03-18 → 2026-03-24 · 2 obs
○ 2026-03-24 15:39:48
●A54.74.120.2012026-03-18 → 2026-03-24 · 3 obs
● 2026-03-18 12:49:30
● 2026-03-24 15:39:48
○A63.35.78.982019-03-20 → 2020-02-20 · 4 obs
● 2020-02-20 03:55:00
○ 2026-03-18 12:49:30
○ 2026-03-24 15:39:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| whoelseisrunning.com | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.32.106
NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for whoelseisrunning.com (unsigned zone)
⏱️ Timing
Total: 250ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 3 | 54.74.120.201, 54.220.54.72... |
| NS | 4 | ns-cloud-a1.googledomains.com, ns-cloud-a3.googledomains.com... |
| SOA | 1 | ns-cloud-a1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)
Analysis
IP Addresses
whoelseisrunning.com points to three IPs: 52.215.253.68, 54.74.120.201 and 54.220.54.72.
Other host names, for instance ec2-54-220-54-72.eu-west-1.compute.amazonaws.com, share IP numbers with whoelseisrunning.com.
Name Servers
whoelseisrunning.com is delegated to four name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.
whoelseisrunning.com at least partially shares name servers with other domains, for instance aamx.com, distributed.live, estudiomata.com, philmckey.com and stencilgram.com.
These name servers are commonly used alongside ns1.mirusresearch.com and ns2.mir.us.
Host names with two IP numbers:
ns-cloud-a1.googledomains.com points to 2001:4860:4802:32::6a and 216.239.32.106; ns-cloud-a2.googledomains.com points to 2001:4860:4802:34::6a and 216.239.34.106; ns-cloud-a3.googledomains.com points to 2001:4860:4802:36::6a and 216.239.36.106; ns-cloud-a4.googledomains.com points to 2001:4860:4802:38::6a and 216.239.38.106.