357townhouse.com - robtex.com
357townhouse.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=1784563327 | ||||||
Same first word
357townhouse.com |
DNS History
13 records (13 active, 0 former)
●NSns-cloud-d1.googledomains.com2026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●NSns-cloud-d2.googledomains.com2026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●NSns-cloud-d3.googledomains.com2026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●NSns-cloud-d4.googledomains.com2026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●MXalt1.aspmx.l.google.com2026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●MXalt2.aspmx.l.google.com2026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●MXalt3.aspmx.l.google.com2026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●MXalt4.aspmx.l.google.com2026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●MXaspmx.l.google.com2026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●A198.185.159.1442026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●A198.185.159.1452026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●A198.49.23.1442026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
●A198.49.23.1452026-05-09 → 2026-07-20 · 2 obs
● 2026-07-20 16:02:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net, m.gtld-servers.net... | - |
| 357townhouse.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.38.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 357townhouse.com (unsigned zone)
⏱️ Timing
Total: 1419ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 198.49.23.145, 198.185.159.144... |
| NS | 4 | ns-cloud-d4.googledomains.com, ns-cloud-d1.googledomains.com... |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | google-site-verification=_V2wsGgNNAlcX06 |
| 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
357townhouse.com points to the four IP addresses 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
Among the host names that share IP numbers with 357townhouse.com are killconflict.com, pc419.com, jungmo.com and two others.
Name Servers
The domain 357townhouse.com is delegated to these four name servers: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com.
There is at least partial name server overlap between 357townhouse.com and other domains — jackdamon.com, ososhomepatioarizona.com, pedicabmedianetwork.com and two more among them.
All four hostnames — ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com — resolve to two IP numbers apiece: ns-cloud-d1.googledomains.com to 216.239.32.109 and 2001:4860:4802:32::6d; ns-cloud-d2.googledomains.com to 216.239.34.109 and 2001:4860:4802:34::6d; ns-cloud-d3.googledomains.com to 216.239.36.109 and 2001:4860:4802:36::6d; ns-cloud-d4.googledomains.com to 216.239.38.109 and 2001:4860:4802:38::6d.
Mail Servers
357townhouse.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
357townhouse.com shares at least some of its mail servers with other domains — for example ns500731.ns500742.ns500731.ns500731.ns500731.ns500742.ns500754.ns500704.ns500688.ns500678.ns500671.ns500671.ns500649.tenderladiesbz.com, ns500731.ns500671.ns500754.ns500742.ns500754.ns500688.ns500705.ns500291.ns500291.ns500671.ns500291.ns500291.ns500131.lustychickser.com, ns500754.ns500754.ns500731.ns500731.ns500671.ns500742.ns500671.ns500705.ns500704.ns500671.lusty(0x736c7574)z.com and two more.
It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to 142.251.167.26 and 2607:f8b0:4004:c1d::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.