m2structural.com - dns.ninja
m2structural.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=1786861839 | ||||||
Same first word
m2structural.com |
DNS History
9 records (8 active, 1 former)
●NSns33.domaincontrol.com2015-06-14 → 2026-08-16 · 2 obs
● 2026-08-16 06:33:36
●NSns34.domaincontrol.com2015-06-14 → 2026-08-16 · 2 obs
● 2026-08-16 06:33:36
●MXalt1.aspmx.l.google.com2015-06-14 → 2026-08-16 · 2 obs
● 2026-08-16 06:33:36
●MXalt2.aspmx.l.google.com2015-06-14 → 2026-08-16 · 2 obs
● 2026-08-16 06:33:36
●MXaspmx.l.google.com2015-06-14 → 2026-08-16 · 2 obs
● 2026-08-16 06:33:36
●MXaspmx2.googlemail.com2015-06-14 → 2026-08-16 · 2 obs
● 2026-08-16 06:33:36
●MXaspmx3.googlemail.com2015-06-14 → 2026-08-16 · 2 obs
● 2026-08-16 06:33:36
●A151.101.130.1592026-07-13 → 2026-08-16 · 3 obs
● 2026-07-13 14:48:32
● 2026-08-16 06:33:36
○A50.63.197.112015-06-14 → 2017-10-26 · 4 obs
● 2017-10-26 19:16:30
○ 2026-07-13 14:48:32
○ 2026-08-16 06:33:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| m2structural.com | ns33.domaincontrol.com, ns34.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.106.17
NS records: ns33.domaincontrol.com, ns34.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for m2structural.com (unsigned zone)
⏱️ Timing
Total: 131ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 151.101.130.159 |
| NS | 2 | ns33.domaincontrol.com, ns34.domaincontrol.com |
| MX | 5 | aspmx2.googlemail.com (pri: 40), alt1.aspmx.l.google.com (pri: 20)... |
| TXT | 3 | nqcn3a6ftk5mj44cihnsbjrfom , er14dkut6titj29sfaq25s6res... |
| SOA | 1 | ns33.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns33.domaincontrol.com, ns33.domaincontrol.com, ns34.domaincontrol.com...)
Analysis
IP Addresses
m2structural.com has exactly one IP address — 151.101.130.159.
smith-equipment.com, experiencedlawyers.ca, lvtc.ca plus two other host names have IP numbers in common with m2structural.com.
Name Servers
m2structural.com uses two name servers for its delegation: ns33.domaincontrol.com and ns34.domaincontrol.com.
The name server configuration of m2structural.com is shared with other domains, for instance newyorktonomad.com, newdp.com, healthcarebirmingham.com and two others.
m2structural.com shares at least some of its name servers with domains including wobbly-canoe.com, tv-tv.com and maple-brownabbott.com.au
The two host names ns33.domaincontrol.com and ns34.domaincontrol.com each have a pair of IP addresses: ns33.domaincontrol.com has 97.74.106.17 and 2603:5:21a1::11, and ns34.domaincontrol.com has 173.201.74.17 and 2603:5:22a1::11.
Mail Servers
m2structural.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by m2structural.com are shared with other domains: ns500731.ns500671.ns500731.ns500731.ns500742.ns500671.ns500704.ns500671.ns500704.ns500704.ns500649.ns500291.ns500666.ns500131.lustychickser.com, ns500754.ns500731.ns500705.ns500704.ns500705.ns500671.ns500291.ns500291.ns500131.lustychickser.com, ns500734.ns500734.ns500699.ns500693.ns500699.ns500693.ns500734.ns500699.ns500683.ns500588.ns500588.ns500588.dtrkdll.com and two others among them.
These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.251.167.26 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.