led25.com - dns.ninja
led25.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=1786394299 | ||||||
MX for
led25.com |
Same first word
led25.com |
Similar names
DNS History
13 records (10 active, 3 former)
●NSevan.ns.cloudflare.com2026-05-14 → 2026-08-10 · 3 obs
● 2026-05-14 18:53:24
● 2026-08-10 20:46:30
●NSmarjory.ns.cloudflare.com2026-05-14 → 2026-08-10 · 3 obs
● 2026-05-14 18:53:24
● 2026-08-10 20:46:30
○NSns4.blueweb.co.kr2015-06-02 → 2017-12-14 · 4 obs
● 2017-12-14 16:00:54
○ 2026-05-14 18:53:24
○ 2026-08-10 20:46:30
○NSns5.blueweb.co.kr2015-06-02 → 2017-12-14 · 4 obs
● 2017-12-14 16:00:54
○ 2026-05-14 18:53:24
○ 2026-08-10 20:46:30
●MXalt1.aspmx.l.google.com2015-06-02 → 2026-08-10 · 2 obs
● 2026-08-10 20:46:30
●MXalt2.aspmx.l.google.com2015-06-02 → 2026-08-10 · 2 obs
● 2026-08-10 20:46:30
●MXaspmx.l.google.com2015-06-02 → 2026-08-10 · 2 obs
● 2026-08-10 20:46:30
●MXaspmx2.googlemail.com2015-06-02 → 2026-08-10 · 2 obs
● 2026-08-10 20:46:30
●MXaspmx3.googlemail.com2015-06-02 → 2026-08-10 · 2 obs
● 2026-08-10 20:46:30
●MXaspmx4.googlemail.com2015-06-02 → 2026-08-10 · 2 obs
● 2026-08-10 20:46:30
●MXaspmx5.googlemail.com2015-06-02 → 2026-08-10 · 2 obs
● 2026-08-10 20:46:30
●MXled25.com2015-06-02 → 2026-08-10 · 2 obs
● 2026-08-10 20:46:30
○A222.102.172.2452015-06-02 → 2017-12-14 · 4 obs
● 2017-12-14 16:00:54
○ 2026-05-14 18:53:24
○ 2026-08-10 20:46:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, b.gtld-servers.net... | - |
| led25.com | evan.ns.cloudflare.com, marjory.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.192.193
NS records: evan.ns.cloudflare.com, marjory.ns.cloudflare.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 413ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | evan.ns.cloudflare.com, marjory.ns.cloudflare.com |
| MX | 8 | aspmx.l.google.com (pri: 10), led25.com (pri: 10)... |
| SOA | 1 | evan.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (evan.ns.cloudflare.com, evan.ns.cloudflare.com, evan.ns.cloudflare.com...)
Analysis
Mail Server Role
led25.com is listed as a mail server for itself.
As mail servers, aspmx2.googlemail.com, aspmx3.googlemail.com and aspmx4.googlemail.com are often used in combination with led25.com.
Name Servers
led25.com has two authoritative name servers — evan.ns.cloudflare.com and marjory.ns.cloudflare.com.
led25.com uses the same name servers as several other domains — among them cliffordhelsel.com, anagrama.casa, hoboleaks.space and two more.
led25.com has at least partial name server overlap with other domains, such as monicacastle.com, porieoritajdosfwrks.site, 777-farofa777.net and two others.
It is common to see these name servers used together with name servers ray.ns.cloudflare.com and kami.ns.cloudflare.com.
Hostnames that resolve to 6 IP addresses:
evan.ns.cloudflare.com points to 108.162.193.165, 172.64.33.165, 173.245.59.165 and 3 other IP addresses.
marjory.ns.cloudflare.com points to 108.162.192.193, 172.64.32.193, 173.245.58.193 and 3 other IP addresses.
Mail Servers
Mail for led25.com is handled by 8 mail servers: led25.com, aspmx2.googlemail.com, aspmx3.googlemail.com and 5 more.
led25.com has at least partial mail server overlap with other domains such as ns500693.ns500734.ns500693.ns500693.ns500734.ns500734.ns500699.ns500693.ns500699.ns500588.ns500699.ns500699.ns500699.ns500683.ns500632.ns500578.ns500110.dtrkdll.com, ns500742.ns500731.ns500754.ns500731.ns500754.ns500731.ns500705.ns500705.ns500688.ns500678.ns500671.lusty(0x736c7574)z.com, ns500759.ns500758.ns500698.ns500698.ns500758.ns500736.ns500735.ns500735.ns500698.ns500736.ns500576.ns500576.ns500576.ns500698.ns500652.trackreceptor.com and two more.
These mail servers commonly co-occur with mail servers aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1b.
aspmx3.googlemail.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx4.googlemail.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.
aspmx5.googlemail.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1b.
aspmx.l.google.com resolves to 192.178.155.26 and 2607:f8b0:4004:c1b::1b.
alt1.aspmx.l.google.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 2800:3f0:4003:c14::1b IP addresses.
The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 2a00:1450:400b:c02::1b IP addresses.
The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 172.253.116.27 IP addresses.