swagsignals.com - robtex.com
swagsignals.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=1784206307 | ||||||
Same first word
swagsignals.com |
DNS History
8 records (8 active, 0 former)
●NSns-cloud-e1.googledomains.com2026-06-11 → 2026-07-16 · 2 obs
● 2026-07-16 13:00:00
●NSns-cloud-e2.googledomains.com2026-06-11 → 2026-07-16 · 2 obs
● 2026-07-16 13:00:00
●NSns-cloud-e3.googledomains.com2026-06-11 → 2026-07-16 · 2 obs
● 2026-07-16 13:00:00
●NSns-cloud-e4.googledomains.com2026-06-11 → 2026-07-16 · 2 obs
● 2026-07-16 13:00:00
●A198.185.159.1442026-06-11 → 2026-07-16 · 2 obs
● 2026-07-16 13:00:00
●A198.185.159.1452026-06-11 → 2026-07-16 · 2 obs
● 2026-07-16 13:00:00
●A198.49.23.1442026-06-11 → 2026-07-16 · 2 obs
● 2026-07-16 13:00:00
●A198.49.23.1452026-06-11 → 2026-07-16 · 2 obs
● 2026-07-16 13:00:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, l.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net... | - |
| swagsignals.com | ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.34.110
NS records: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for swagsignals.com (unsigned zone)
⏱️ Timing
Total: 504ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 198.49.23.145, 198.185.159.144... |
| NS | 4 | ns-cloud-e2.googledomains.com, ns-cloud-e4.googledomains.com... |
| TXT | 1 | v=spf1 -all |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h2", |
| SOA | 1 | ns-cloud-e1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-e1.googledomains.com, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com...)
Analysis
IP Addresses
swagsignals.com directs to four IP numbers, which are 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
Two other host names, along with chanelquisol.com, lektionen.dk and truedeliverysolutions.net, also share IP numbers with swagsignals.com.
Name Servers
The NS records for swagsignals.com point to four name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
The name servers of swagsignals.com overlap at least partially with those of other domains — among them sagecohenglobal.com, uberpeople.net, vagdrivers.net and two more.
Each of the four hosts ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com has two IP addresses. ns-cloud-e1.googledomains.com points to 216.239.32.110 and 2001:4860:4802:32::6e. ns-cloud-e2.googledomains.com points to 216.239.34.110 and 2001:4860:4802:34::6e. ns-cloud-e3.googledomains.com points to 216.239.36.110 and 2001:4860:4802:36::6e. ns-cloud-e4.googledomains.com points to 216.239.38.110 and 2001:4860:4802:38::6e.