liamforcongress.com - robtex.com
liamforcongress.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=1785747077 | ||||||
Same first word
liamforcongress.com |
DNS History
8 records (8 active, 0 former)
●NSns-cloud-d1.googledomains.com2026-07-12 → 2026-08-03 · 2 obs
● 2026-08-03 09:02:52
●NSns-cloud-d2.googledomains.com2026-07-12 → 2026-08-03 · 2 obs
● 2026-08-03 09:02:52
●NSns-cloud-d3.googledomains.com2026-07-12 → 2026-08-03 · 2 obs
● 2026-08-03 09:02:52
●NSns-cloud-d4.googledomains.com2026-07-12 → 2026-08-03 · 2 obs
● 2026-08-03 09:02:52
●A198.185.159.1442026-07-12 → 2026-08-03 · 2 obs
● 2026-08-03 09:02:52
●A198.185.159.1452026-07-12 → 2026-08-03 · 2 obs
● 2026-08-03 09:02:52
●A198.49.23.1442026-07-12 → 2026-08-03 · 2 obs
● 2026-08-03 09:02:52
●A198.49.23.1452026-07-12 → 2026-08-03 · 2 obs
● 2026-08-03 09:02:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| liamforcongress.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 liamforcongress.com (unsigned zone)
⏱️ Timing
Total: 278ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 198.185.159.145, 198.49.23.144... |
| NS | 4 | ns-cloud-d4.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
liamforcongress.com resolves to 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 liamforcongress.com are kinujapan.com, cmelater.net, wonderwomanmethod.com.au and two others.
Name Servers
The domain liamforcongress.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.
liamforcongress.com partially shares its NS delegation with several other domains, including monety.com, 1856ventures.net, meritamerica.org and two others.
ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com each carry two IP addresses. ns-cloud-d1.googledomains.com has 216.239.32.109 and 2001:4860:4802:32::6d; ns-cloud-d2.googledomains.com has 216.239.34.109 and 2001:4860:4802:34::6d; ns-cloud-d3.googledomains.com has 216.239.36.109 and 2001:4860:4802:36::6d; ns-cloud-d4.googledomains.com has 216.239.38.109 and 2001:4860:4802:38::6d.