madcore.com - dns.ninja
madcore.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=1785437062 | ||||||
Subdomains
Same first word
Similar names
DNS History
20 records (11 active, 9 former)
●NSnaya.ns.cloudflare.com2026-03-03 → 2026-07-30 · 3 obs
● 2026-03-03 15:34:12
● 2026-07-30 19:07:22
○NSns33.domaincontrol.com2015-06-14 → 2018-10-08 · 4 obs
● 2018-10-08 18:55:02
○ 2026-03-03 15:34:12
○ 2026-07-30 19:07:22
○NSns34.domaincontrol.com2015-06-14 → 2018-10-08 · 4 obs
● 2018-10-08 18:55:02
○ 2026-03-03 15:34:12
○ 2026-07-30 19:07:22
●NSrodrigo.ns.cloudflare.com2026-03-03 → 2026-07-30 · 3 obs
● 2026-03-03 15:34:12
● 2026-07-30 19:07:22
●MXalt1.aspmx.l.google.com2015-06-14 → 2026-07-30 · 2 obs
● 2026-07-30 19:07:22
●MXalt2.aspmx.l.google.com2015-06-14 → 2026-07-30 · 2 obs
● 2026-07-30 19:07:22
●MXaspmx.l.google.com2015-06-14 → 2026-07-30 · 2 obs
● 2026-07-30 19:07:22
●MXaspmx2.googlemail.com2015-06-14 → 2026-07-30 · 2 obs
● 2026-07-30 19:07:22
●MXaspmx3.googlemail.com2015-06-14 → 2026-07-30 · 2 obs
● 2026-07-30 19:07:22
●A104.21.86.52026-03-03 → 2026-07-30 · 6 obs
● 2026-03-03 15:34:12
● 2026-04-19 16:43:58
○ 2026-05-06 05:25:58
● 2026-06-01 11:27:28
● 2026-07-30 19:07:22
●A172.67.213.812026-03-03 → 2026-07-30 · 6 obs
● 2026-03-03 15:34:12
● 2026-04-19 16:43:58
○ 2026-05-06 05:25:58
● 2026-06-01 11:27:28
● 2026-07-30 19:07:22
○A188.114.96.02026-05-06 → 2026-05-06 · 5 obs
○ 2026-04-19 16:43:58
● 2026-05-06 05:25:58
○ 2026-06-01 11:27:28
○ 2026-07-30 19:07:22
○A188.114.97.02026-05-06 → 2026-05-06 · 5 obs
○ 2026-04-19 16:43:58
● 2026-05-06 05:25:58
○ 2026-06-01 11:27:28
○ 2026-07-30 19:07:22
○A2606:4700:3030::6815:56052026-03-03 → 2026-06-01 · 7 obs
● 2026-03-03 15:34:12
● 2026-04-19 16:43:58
○ 2026-05-06 05:25:58
● 2026-06-01 11:27:28
○ 2026-07-09 11:57:34
○ 2026-07-30 19:07:22
○A2606:4700:3030::ac43:d5512026-03-03 → 2026-06-01 · 7 obs
● 2026-03-03 15:34:12
● 2026-04-19 16:43:58
○ 2026-05-06 05:25:58
● 2026-06-01 11:27:28
○ 2026-07-09 11:57:34
○ 2026-07-30 19:07:22
●A2606:4700:3033::ac43:d5512026-07-09 → 2026-07-30 · 3 obs
● 2026-07-09 11:57:34
● 2026-07-30 19:07:22
●A2606:4700:3035::6815:56052026-07-09 → 2026-07-30 · 3 obs
● 2026-07-09 11:57:34
● 2026-07-30 19:07:22
○A2a06:98c1:3120::2026-05-06 → 2026-05-06 · 5 obs
○ 2026-04-19 16:43:58
● 2026-05-06 05:25:58
○ 2026-06-01 11:27:28
○ 2026-07-30 19:07:22
○A2a06:98c1:3121::2026-05-06 → 2026-05-06 · 5 obs
○ 2026-04-19 16:43:58
● 2026-05-06 05:25:58
○ 2026-06-01 11:27:28
○ 2026-07-30 19:07:22
○A66.175.223.212015-06-14 → 2018-10-08 · 4 obs
● 2018-10-08 18:55:02
○ 2026-03-03 15:34:12
○ 2026-07-30 19:07:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, b.gtld-servers.net, d.gtld-servers.net, i.gtld-servers.net... | - |
| madcore.com | naya.ns.cloudflare.com, rodrigo.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.195.78
NS records: naya.ns.cloudflare.com, rodrigo.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for madcore.com (unsigned zone)
⏱️ Timing
Total: 810ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 172.67.213.81, 104.21.86.5 |
| AAAA | 2 | 2606:4700:3033::ac43:d551, 2606:4700:3035::6815:5605 |
| NS | 2 | naya.ns.cloudflare.com, rodrigo.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)... |
| TXT | 4 | google-site-verification=RrJWlfX3DRZ9q4V, google-site-verification=pZq-UzaoWZmjuPR... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | naya.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (naya.ns.cloudflare.com, naya.ns.cloudflare.com, naya.ns.cloudflare.com...)
Analysis
Hierarchy
madcore.com is the parent domain of ca.madcore.com and www.madcore.com.
IP Addresses
madcore.com resolves to four IP addresses: 104.21.86.5, 172.67.213.81, 2606:4700:3033::ac43:d551 and 2606:4700:3035::6815:5605.
Additional host names — horseracing.com, www.campion.edu.gr, pango.lv and two others — share IP numbers with madcore.com.
Name Servers
madcore.com uses two name servers for its delegation: naya.ns.cloudflare.com and rodrigo.ns.cloudflare.com.
madcore.com shares its name server setup with other domains, including shiny.today, leveljam.com, solertachainvia-soft.com and two others.
madcore.com partially shares its NS delegation with several other domains, including senior-law.com, zeitgeist.co, lunaris.moe and two others.
These name servers regularly co-occur with the name servers monroe.ns.cloudflare.com, ashton.ns.cloudflare.com and hazel.ns.cloudflare.com.
Host names with 6 IP numbers:
Hostname naya.ns.cloudflare.com directs to 108.162.194.242, 162.159.38.242 and 172.64.34.242 along with 3 other IP addresses.
Hostname rodrigo.ns.cloudflare.com directs to 108.162.195.78, 162.159.44.78 and 172.64.35.78 along with 3 other IP addresses.
Mail Servers
madcore.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
madcore.com shares mail servers — at least in part — with other domains, including hakimane.com, knoxis.com, ns500671.ns500742.ns500742.ns500754.ns500671.ns500705.ns500678.ns500153.tenderladiesbz.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.
Host names with two IP numbers:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 172.253.115.27 and 2607:f8b0:4004:c0b::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.