structuresing.com - dns.ninja
structuresing.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=1783731642 | ||||||
Same first word
structuresing.com |
Similar names
DNS History
10 records (10 active, 0 former)
●NSns-cloud-e1.googledomains.com2026-05-25 → 2026-07-11 · 2 obs
● 2026-07-11 01:14:12
●NSns-cloud-e2.googledomains.com2026-05-25 → 2026-07-11 · 2 obs
● 2026-07-11 01:14:12
●NSns-cloud-e3.googledomains.com2026-05-25 → 2026-07-11 · 2 obs
● 2026-07-11 01:14:12
●NSns-cloud-e4.googledomains.com2026-05-25 → 2026-07-11 · 2 obs
● 2026-07-11 01:14:12
●MXalt1.aspmx.l.google.com2026-05-25 → 2026-07-11 · 2 obs
● 2026-07-11 01:14:12
●MXalt2.aspmx.l.google.com2026-05-25 → 2026-07-11 · 2 obs
● 2026-07-11 01:14:12
●MXalt3.aspmx.l.google.com2026-05-25 → 2026-07-11 · 2 obs
● 2026-07-11 01:14:12
●MXalt4.aspmx.l.google.com2026-05-25 → 2026-07-11 · 2 obs
● 2026-07-11 01:14:12
●MXaspmx.l.google.com2026-05-25 → 2026-07-11 · 2 obs
● 2026-07-11 01:14:12
●A198.185.159.1442026-05-25 → 2026-07-11 · 2 obs
● 2026-07-11 01:14:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, g.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net... | - |
| structuresing.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.32.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
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 414ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 198.185.159.144 |
| NS | 4 | ns-cloud-e1.googledomains.com, ns-cloud-e4.googledomains.com... |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| 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
structuresing.com has exactly one IP address — 198.185.159.144.
percussionportal.com, factualwind.com, adeptscholarssociety.com plus two other host names have IP numbers in common with structuresing.com.
Name Servers
Four name servers handle the delegation for structuresing.com: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com.
structuresing.com shares at least some of its name servers with other domains, including perfectlyamanda.com, nlytnwellness.com, architecturework.com and two others.
The host names ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com and ns-cloud-e4.googledomains.com each resolve to two IP addresses: ns-cloud-e1.googledomains.com resolves to 216.239.32.110 and 2001:4860:4802:32::6e; ns-cloud-e2.googledomains.com resolves to 216.239.34.110 and 2001:4860:4802:34::6e; ns-cloud-e3.googledomains.com resolves to 216.239.36.110 and 2001:4860:4802:36::6e; ns-cloud-e4.googledomains.com resolves to 216.239.38.110 and 2001:4860:4802:38::6e.
Mail Servers
Mail for structuresing.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by structuresing.com are shared with other domains: ns500698.ns500698.ns500698.ns500698.ns500698.ns500736.ns500698.ns500736.ns500735.ns500576.ns500576.ns500698.ns500686.ns500576.ns500619.trackreceptor.com, ns500734.ns500699.ns500693.ns500693.ns500699.ns500693.ns500699.ns500588.ns500699.ns500588.ns500693.ns500683.ns500588.ns500699.ns500683.ns500683.ns500588.dtrkdll.com, ns500758.ns500759.ns500759.ns500698.ns500576.ns500708.ns500576.ns500576.ns500708.ns500619.ns500576.ns500576.ns500652.ns500652.tracksymphony.com and two others among them.
It is common to find these mail servers paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and aspmx2.googlemail.com, as well as two others.
Host names pointing to two IP addresses:
aspmx.l.google.com has two IP addresses: 142.251.16.26 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com has two IP addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com has two IP addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com has two IP addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com has two IP addresses: 172.253.157.27 and 2a00:1450:400c:c23::1b.