prodragon.com - dns.ninja
prodragon.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 91.195.241.232🇩🇪 SEDO91.195.240.0/23 -NET-PI | ||||||
| NS | sl1.sedo.com ⭐ | ||||||
| A | 91.195.240.173🇩🇪 SEDO91.195.240.0/23 -NET-PI | ||||||
| NS | sl2.sedo.com | ||||||
| A | 91.195.241.173🇩🇪 SEDO91.195.240.0/23 -NET-PI | ||||||
| MX | localhost ⭐ | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | sl1.sedo.comhostmaster@sedo.de 2018-05-16 #1 | ||||||
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=1785182407 | ||||||
Same first word
prodragon.com |
prodragon.com.vn |
Similar names
androprog.ru |
radnorgop.org |
dragonpro.com |
dragonpro.pl |
(0x706f726e)ograd.ru |
(0x706f726e)ograd.click |
garonprod.com |
proandgro.com |
DNS History
24 records (4 active, 20 former)
○NSbuy.internettraffic.com2015-06-21 → 2016-04-20 · 4 obs
● 2016-04-20 07:07:16
○ 2017-01-08 02:46:50
○ 2026-07-27 20:12:56
○NSlaunch1.spaceship.net2026-03-25 → 2026-03-25 · 4 obs
● 2026-03-25 09:10:38
○ 2026-03-26 13:13:36
○ 2026-07-27 20:12:56
○NSlaunch2.spaceship.net2026-03-25 → 2026-03-25 · 4 obs
● 2026-03-25 09:10:38
○ 2026-03-26 13:13:36
○ 2026-07-27 20:12:56
○NSns1.atom.com2026-03-26 → 2026-04-07 · 5 obs
● 2026-03-26 13:13:36
● 2026-04-07 23:05:36
○ 2026-05-07 22:10:18
○ 2026-07-27 20:12:56
○NSns1.prodragon.com2026-05-07 → 2026-05-07 · 4 obs
● 2026-05-07 22:10:18
○ 2026-07-27 20:12:54
○ 2026-07-27 20:12:56
○NSns1.sudos.co2026-05-07 → 2026-05-07 · 4 obs
● 2026-05-07 22:10:18
○ 2026-07-27 20:12:54
○ 2026-07-27 20:12:56
○NSns1.uniregistrymarket.link2017-01-08 → 2017-01-08 · 4 obs
● 2017-01-08 02:46:50
○ 2018-06-18 01:31:38
○ 2026-07-27 20:12:56
○NSns2.atom.com2026-03-26 → 2026-04-07 · 5 obs
● 2026-03-26 13:13:36
● 2026-04-07 23:05:36
○ 2026-05-07 22:10:18
○ 2026-07-27 20:12:56
○NSns2.sudos.co2026-05-07 → 2026-05-07 · 4 obs
● 2026-05-07 22:10:18
○ 2026-07-27 20:12:54
○ 2026-07-27 20:12:56
○NSns2.uniregistrymarket.link2017-01-08 → 2017-01-08 · 4 obs
● 2017-01-08 02:46:50
○ 2018-06-18 01:31:38
○ 2026-07-27 20:12:56
○NSns3.afternic.com2018-06-18 → 2018-06-18 · 4 obs
● 2018-06-18 01:31:38
○ 2026-03-25 09:10:38
○ 2026-07-27 20:12:56
○NSns4.afternic.com2018-06-18 → 2018-06-18 · 4 obs
● 2018-06-18 01:31:38
○ 2026-03-25 09:10:38
○ 2026-07-27 20:12:56
○NSsell.internettraffic.com2015-06-21 → 2016-04-20 · 4 obs
● 2016-04-20 07:07:16
○ 2017-01-08 02:46:50
○ 2026-07-27 20:12:56
●NSsl1.sedo.com2026-07-27 → 2026-07-27 · 3 obs
● 2026-07-27 20:12:54
● 2026-07-27 20:12:56
●NSsl2.sedo.com2026-07-27 → 2026-07-27 · 3 obs
● 2026-07-27 20:12:54
● 2026-07-27 20:12:56
●MXlocalhost2026-07-27 → 2026-07-27 · 2 obs
● 2026-07-27 20:12:56
○A165.140.157.132026-05-07 → 2026-05-07 · 4 obs
● 2026-05-07 22:10:18
○ 2026-07-27 20:12:54
○ 2026-07-27 20:12:56
○A44.232.173.2492026-03-25 → 2026-03-25 · 4 obs
● 2026-03-25 09:10:38
○ 2026-03-26 13:13:36
○ 2026-07-27 20:12:56
○A52.20.84.622026-03-26 → 2026-04-07 · 5 obs
● 2026-03-26 13:13:36
● 2026-04-07 23:05:36
○ 2026-05-07 22:10:18
○ 2026-07-27 20:12:56
○A52.40.42.1132026-03-25 → 2026-03-25 · 4 obs
● 2026-03-25 09:10:38
○ 2026-03-26 13:13:36
○ 2026-07-27 20:12:56
○A54.208.77.1242018-06-18 → 2018-06-18 · 4 obs
● 2018-06-18 01:31:38
○ 2026-03-25 09:10:38
○ 2026-07-27 20:12:56
○A69.172.201.1532016-04-20 → 2017-01-08 · 5 obs
● 2016-04-20 07:07:16
● 2017-01-08 02:46:50
○ 2018-06-18 01:31:38
○ 2026-07-27 20:12:56
○A69.172.201.2082015-06-21 → 2016-01-21 · 4 obs
● 2016-01-21 18:52:48
○ 2016-04-20 07:07:16
○ 2026-07-27 20:12:56
●A91.195.241.2322026-07-27 → 2026-07-27 · 3 obs
● 2026-07-27 20:12:54
● 2026-07-27 20:12:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| prodragon.com | sl1.sedo.com, sl2.sedo.com | 2 records |
✅ Authoritative Response
Server:91.195.240.173
NS records: sl1.sedo.com, sl2.sedo.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for prodragon.com (unsigned zone)
⏱️ Timing
Total: 323ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.241.232 |
| NS | 2 | sl2.sedo.com, sl1.sedo.com |
| MX | 1 | localhost (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | sl1.sedo.com hostmaster.sedo.de |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (sl1.sedo.com, sl2.sedo.com)
Analysis
IP Addresses
prodragon.com has exactly one IP address — 91.195.241.232.
mail.fotos(0x787878).de, woden.online, mx.mx.m2service.de plus two other host names have IP numbers in common with prodragon.com.
Name Servers
prodragon.com uses two name servers for its delegation: sl1.sedo.com and sl2.sedo.com.
The name server configuration of prodragon.com is shared with other domains, for instance pimpf.de, mail.o2d.eu, ucw.info and two others.
sl1.sedo.com resolves to 91.195.240.173. sl2.sedo.com resolves to 91.195.241.173. Both host names point to a single IP number.
Mail Servers
prodragon.com uses one mail server — localhost.
The mail server setup of prodragon.com matches that of other domains such as moving2tucson.net, pcng.de, www.denied.com and two others.