milesign.com - dns.ninja
milesign.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=1786108694 | ||||||
Same first word
milesign.com |
Similar names
DNS History
8 records (7 active, 1 former)
●NSns25.domaincontrol.com2015-07-15 → 2026-08-07 · 2 obs
● 2026-08-07 13:38:02
●NSns26.domaincontrol.com2015-07-15 → 2026-08-07 · 2 obs
● 2026-08-07 13:38:02
●MXalt1.aspmx.l.google.com2015-07-15 → 2026-08-07 · 2 obs
● 2026-08-07 13:38:02
●MXalt2.aspmx.l.google.com2015-07-15 → 2026-08-07 · 2 obs
● 2026-08-07 13:38:02
●MXaspmx.l.google.com2015-07-15 → 2026-08-07 · 2 obs
● 2026-08-07 13:38:02
●MXaspmx2.googlemail.com2015-07-15 → 2026-08-07 · 2 obs
● 2026-08-07 13:38:02
●MXaspmx3.googlemail.com2015-07-15 → 2026-08-07 · 2 obs
● 2026-08-07 13:38:02
○A50.63.202.602015-07-15 → 2017-02-14 · 4 obs
● 2017-02-14 06:03:08
○ 2019-01-26 19:59:12
○ 2026-08-07 13:38:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net, i.gtld-servers.net... | - |
| milesign.com | ns25.domaincontrol.com, ns26.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.70.13
NS records: ns25.domaincontrol.com, ns26.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for milesign.com (unsigned zone)
⏱️ Timing
Total: 188ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns25.domaincontrol.com, ns26.domaincontrol.com |
| MX | 5 | aspmx2.googlemail.com (pri: 40), aspmx3.googlemail.com (pri: 50)... |
| SOA | 1 | ns25.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns25.domaincontrol.com, ns25.domaincontrol.com, ns26.domaincontrol.com...)
Analysis
Name Servers
milesign.com is served by two delegated name servers, ns25.domaincontrol.com and ns26.domaincontrol.com.
milesign.com uses the same name servers as several other domains — among them rocksjewelrygiftshome.com, patch-ai.com, painframe.com and two more.
Each of the two host names carries two IP addresses: ns25.domaincontrol.com points to 97.74.102.13 and 2603:5:2161::d, and ns26.domaincontrol.com points to 173.201.70.13 and 2603:5:2261::d.
Mail Servers
milesign.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
milesign.com has at least partial mail server overlap with other domains such as uzume.com, icaruslaw.com, zecovery.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com maps to two IP addresses — 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com maps to two IP addresses — 192.178.155.26 and 2607:f8b0:4004:c09::1a.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.
These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 108.177.123.26 IP addresses.
These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 2a00:1450:400b:c02::1a IP addresses.
These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 172.253.116.27 IP addresses.