exploit0.com - dns.ninja
exploit0.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=1788945498 | ||||||
Same first word
exploit0.com |
Similar names
Previous names
Next names
DNS History
8 records (4 active, 4 former)
βNSbill.ns.cloudflare.com2026-08-24 β 2026-09-09 Β· 3 obs
β 2026-08-24 13:00:24
β 2026-09-09 09:29:50
βNSns73.domaincontrol.com2016-12-17 β 2018-06-23 Β· 4 obs
β 2018-06-23 18:16:54
β 2026-08-24 13:00:24
β 2026-09-09 09:29:50
βNSns74.domaincontrol.com2016-12-17 β 2018-06-23 Β· 4 obs
β 2018-06-23 18:16:54
β 2026-08-24 13:00:24
β 2026-09-09 09:29:50
βNSveda.ns.cloudflare.com2026-08-24 β 2026-09-09 Β· 3 obs
β 2026-08-24 13:00:24
β 2026-09-09 09:29:50
βMXexploit0-com.mail.protection.outlook.com2016-12-17 β 2018-06-23 Β· 4 obs
β 2018-06-23 18:16:54
β 2026-08-24 13:00:24
β 2026-09-09 09:29:50
βMXmx1.alias.proton.me2026-08-24 β 2026-09-09 Β· 3 obs
β 2026-08-24 13:00:24
β 2026-09-09 09:29:50
βMXmx2.alias.proton.me2026-08-24 β 2026-09-09 Β· 3 obs
β 2026-08-24 13:00:24
β 2026-09-09 09:29:50
βA184.168.221.372016-12-17 β 2018-06-23 Β· 4 obs
β 2018-06-23 18:16:54
β 2026-08-24 13:00:24
β 2026-09-09 09:29:50
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| exploit0.com | bill.ns.cloudflare.com, veda.ns.cloudflare.com | 12 records |
β Authoritative Response
Server:108.162.194.147
NS records: bill.ns.cloudflare.com, veda.ns.cloudflare.com
π DNSSEC Status
π Secure (DNSSEC validated)
Chain of trust verified from root to domain
β±οΈ Timing
Total: 921ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | bill.ns.cloudflare.com, veda.ns.cloudflare.com |
| MX | 2 | mx1.alias.proton.me (pri: 10), mx2.alias.proton.me (pri: 20) |
| TXT | 2 | pm-verification=dgeahcnfimnvdfszfkhvzjyt, v=spf1 include:alias.proton.me ~all |
| SOA | 1 | bill.ns.cloudflare.com dns.cloudflare.co |
π Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (bill.ns.cloudflare.com, bill.ns.cloudflare.com, bill.ns.cloudflare.com...)
Analysis
Name Servers
Two name servers handle the delegation for exploit0.com: bill.ns.cloudflare.com and veda.ns.cloudflare.com.
exploit0.com shares its NS records with other domains, for example fiowersfluffy02-7cc.workers.dev, salescaptain.com, deivid9044.workers.dev and two others.
There is at least partial name server overlap between exploit0.com and other domains β arax17.workers.dev, nene57.workers.dev, plantculturehub.com and two more among them.
These name servers frequently co-occur with the name servers love.ns.cloudflare.com and ganz.ns.cloudflare.com.
DNS names with 6 IP addresses:
bill.ns.cloudflare.com resolves to 108.162.193.74, 172.64.33.74 and 173.245.59.74 among others, with 3 other IP addresses in total.
veda.ns.cloudflare.com resolves to 108.162.194.147, 162.159.38.147 and 172.64.34.147 among others, with 3 other IP addresses in total.
Mail Servers
exploit0.com is served by two mail servers, mx1.alias.proton.me and mx2.alias.proton.me.
Among the domains sharing a mail server setup with exploit0.com are timelost.de, justforjunkmail.com, dontsellthis.com and two others.
There is at least a partial MX overlap between exploit0.com and other domains, including flurinryffel.ch, hamedina.net, paher.org and two others.
These mail servers are routinely seen in conjunction with the mail servers mail.protonmail.ch and mailsec.protonmail.ch.
mx1.alias.proton.me and mx2.alias.proton.me each point to two IP numbers β 176.119.200.136 and 185.205.70.136 β making both hosts identical in their DNS resolution.
mx1.alias.proton.me along with mx2.alias.proton.me each resolve to 176.119.200.136 IP addresses.
mx1.alias.proton.me along with mx2.alias.proton.me each resolve to 185.205.70.136 IP addresses.