jpre.com - dns.ninja

jpre.com

DNSSEC⚠️ Not signed
A91.195.241.232🇩🇪 SEDO91.195.240.0/23 -NET-PI
NSsl1.sedo.com ⭐
A91.195.240.173🇩🇪 SEDO91.195.240.0/23 -NET-PI
NSsl2.sedo.com
A91.195.241.173🇩🇪 SEDO91.195.240.0/23 -NET-PI
MXlocalhost ⭐
TXTv=spf1 -all
SOAsl1.sedo.comhostmaster@sedo.de 2018-05-16 #1

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1783941437

Same first word

jpre.com
jpre.info
jpre.co.uk
jpre.ca
jpre.mine.nu
jpre.de

Similar names

epjr.jp
pjer.ca
jerp.com
jerp.ir
ejrp.cn
jrep.info
pejr.com
jerp.cn
jerp.de
prej.com
erjp.co.jp
jper.info
pjer.cz
pjer.se
perj.cn
jrep.co.jp
jrpe.com
erpj.cn
rjpe.com
jper.me
jper.com
jrep.org
pjer.nl
jrep.or.jp
prje.com
jerp.net
perj.org
jrep.jp
ejpr.de
eprj.pl
jper.com.hk
jerp.nu
pejr.info
rjep.ru
jerp.com.br
jper.se
eprj.co.uk
jper.de
prej.net
jrep.de
perj.dk
eprj.ru
epjr.xyz
eprj.biz
epjr.com.br
jerp.tv
ejpr.co.kr
pjre.com.au
jepr.nl
jrep.ru
prej.de
prej.lv
jrep.com

DNS History

30 records (4 active, 26 former)

2008201020122014201620182020202220242026NSsl1.sedo.comsl2.sedo.comns.uniregistry.netns1.dsredirection.comns1.fabulous.comns1.uniregistry-dns.comns1.uniregistry-dns.netns1cvw.name.comns2.dsredirection.comns2.fabulous.comns2.uniregistry-dns.comns2.uniregistry-dns.netns2bkr.name.comns3npv.name.comns4clq.name.comMXlocalhostmail.b-io.coA91.195.241.232162.242.150.89176.34.241.253208.48.81.133208.48.81.134208.48.81.179208.73.212.1223.253.58.22754.205.101.8564.15.205.10064.15.205.10175.126.101.24898.124.245.24
○NSns.uniregistry.net2016-09-12 → 2016-09-12 · 4 obs
○ 2016-03-17 23:34:12
● 2016-09-12 17:30:00
○ 2017-04-25 08:26:36
○ 2026-07-13 11:40:36
○NSns1.dsredirection.com2007-11-15 → 2007-11-15 · 3 obs
● 2007-11-15 00:49:18
○ 2015-08-08 09:54:00
○ 2026-07-13 11:40:36
○NSns1.fabulous.com2015-08-08 → 2016-03-17 · 5 obs
○ 2007-11-15 00:49:18
● 2015-08-08 09:54:00
● 2016-03-17 23:34:12
○ 2016-09-12 17:30:00
○ 2026-07-13 11:40:36
○NSns1.uniregistry-dns.com2016-09-12 → 2016-09-12 · 4 obs
○ 2016-03-17 23:34:12
● 2016-09-12 17:30:00
○ 2017-04-25 08:26:36
○ 2026-07-13 11:40:36
○NSns1.uniregistry-dns.net2016-09-12 → 2016-09-12 · 4 obs
○ 2016-03-17 23:34:12
● 2016-09-12 17:30:00
○ 2017-04-25 08:26:36
○ 2026-07-13 11:40:36
○NSns1cvw.name.com2017-04-25 → 2017-04-25 · 4 obs
○ 2016-09-12 17:30:00
● 2017-04-25 08:26:36
○ 2026-02-19 13:56:56
○ 2026-07-13 11:40:36
○NSns2.dsredirection.com2007-11-15 → 2007-11-15 · 3 obs
● 2007-11-15 00:49:18
○ 2015-08-08 09:54:00
○ 2026-07-13 11:40:36
○NSns2.fabulous.com2015-08-08 → 2016-03-17 · 5 obs
○ 2007-11-15 00:49:18
● 2015-08-08 09:54:00
● 2016-03-17 23:34:12
○ 2016-09-12 17:30:00
○ 2026-07-13 11:40:36
○NSns2.uniregistry-dns.com2016-09-12 → 2016-09-12 · 4 obs
○ 2016-03-17 23:34:12
● 2016-09-12 17:30:00
○ 2017-04-25 08:26:36
○ 2026-07-13 11:40:36
○NSns2.uniregistry-dns.net2016-09-12 → 2016-09-12 · 4 obs
○ 2016-03-17 23:34:12
● 2016-09-12 17:30:00
○ 2017-04-25 08:26:36
○ 2026-07-13 11:40:36
○NSns2bkr.name.com2017-04-25 → 2017-04-25 · 4 obs
○ 2016-09-12 17:30:00
● 2017-04-25 08:26:36
○ 2026-02-19 13:56:56
○ 2026-07-13 11:40:36
○NSns3npv.name.com2017-04-25 → 2017-04-25 · 4 obs
○ 2016-09-12 17:30:00
● 2017-04-25 08:26:36
○ 2026-02-19 13:56:56
○ 2026-07-13 11:40:36
○NSns4clq.name.com2017-04-25 → 2017-04-25 · 4 obs
○ 2016-09-12 17:30:00
● 2017-04-25 08:26:36
○ 2026-02-19 13:56:56
○ 2026-07-13 11:40:36
●NSsl1.sedo.com2026-02-19 → 2026-07-13 · 3 obs
○ 2017-04-25 08:26:36
● 2026-02-19 13:56:56
● 2026-07-13 11:40:36
●NSsl2.sedo.com2026-02-19 → 2026-07-13 · 3 obs
○ 2017-04-25 08:26:36
● 2026-02-19 13:56:56
● 2026-07-13 11:40:36
●MXlocalhost2026-02-19 → 2026-07-13 · 6 obs
○ 2016-09-12 17:30:00
● 2026-02-19 13:56:56
● 2026-03-02 15:39:54
○ 2026-03-03 23:20:18
● 2026-03-29 11:33:48
● 2026-07-13 11:40:36
○MXmail.b-io.co2015-08-08 → 2016-03-17 · 5 obs
○ 2007-11-15 00:49:18
● 2015-08-08 09:54:00
● 2016-03-17 23:34:12
○ 2016-09-12 17:30:00
○ 2026-07-13 11:40:36
○A162.242.150.892016-09-12 → 2016-09-12 · 4 obs
○ 2016-03-17 23:34:12
● 2016-09-12 17:30:00
○ 2017-04-25 08:26:36
○ 2026-07-13 11:40:36
○A176.34.241.2532016-09-12 → 2016-09-12 · 4 obs
○ 2016-03-17 23:34:12
● 2016-09-12 17:30:00
○ 2017-04-25 08:26:36
○ 2026-07-13 11:40:36
○A208.48.81.1332015-08-08 → 2015-12-01 · 5 obs
○ 2007-11-15 00:49:18
● 2015-08-08 09:54:00
● 2015-12-01 00:59:00
○ 2016-03-17 23:34:12
○ 2026-07-13 11:40:36
○A208.48.81.1342015-08-08 → 2015-12-01 · 5 obs
○ 2007-11-15 00:49:18
● 2015-08-08 09:54:00
● 2015-12-01 00:59:00
○ 2016-03-17 23:34:12
○ 2026-07-13 11:40:36
○A208.48.81.1792015-08-08 → 2015-08-08 · 4 obs
○ 2007-11-15 00:49:18
● 2015-08-08 09:54:00
○ 2026-02-19 13:56:56
○ 2026-07-13 11:40:36
○A208.73.212.122007-11-15 → 2007-11-15 · 3 obs
● 2007-11-15 00:49:18
○ 2015-08-08 09:54:00
○ 2026-07-13 11:40:36
○A23.253.58.2272016-09-12 → 2016-09-12 · 4 obs
○ 2016-03-17 23:34:12
● 2016-09-12 17:30:00
○ 2017-04-25 08:26:36
○ 2026-07-13 11:40:36
○A54.205.101.852016-09-12 → 2016-09-12 · 4 obs
○ 2016-03-17 23:34:12
● 2016-09-12 17:30:00
○ 2017-04-25 08:26:36
○ 2026-07-13 11:40:36
○A64.15.205.1002015-08-08 → 2015-12-01 · 5 obs
○ 2007-11-15 00:49:18
● 2015-08-08 09:54:00
● 2015-12-01 00:59:00
○ 2016-03-17 23:34:12
○ 2026-07-13 11:40:36
○A64.15.205.1012015-08-08 → 2015-12-01 · 5 obs
○ 2007-11-15 00:49:18
● 2015-08-08 09:54:00
● 2015-12-01 00:59:00
○ 2016-03-17 23:34:12
○ 2026-07-13 11:40:36
○A75.126.101.2482017-04-25 → 2017-04-25 · 4 obs
○ 2016-09-12 17:30:00
● 2017-04-25 08:26:36
○ 2026-02-19 13:56:56
○ 2026-07-13 11:40:36
●A91.195.241.2322026-02-19 → 2026-07-13 · 6 obs
○ 2017-04-25 08:26:36
● 2026-02-19 13:56:56
● 2026-03-02 15:39:54
○ 2026-03-03 23:20:18
● 2026-03-29 11:33:48
● 2026-07-13 11:40:36
○A98.124.245.242016-03-17 → 2016-03-17 · 4 obs
○ 2015-12-01 00:59:00
● 2016-03-17 23:34:12
○ 2016-09-12 17:30:00
○ 2026-07-13 11:40:36

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coml.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...-
jpre.comsl1.sedo.com, sl2.sedo.com2 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 jpre.com (unsigned zone)

⏱️ Timing

Total: 464ms | Queries: -

📄 Records

TypeCountSample Data
A191.195.241.232
NS2sl2.sedo.com, sl1.sedo.com
MX1localhost (pri: 0)
TXT1v=spf1 -all
SOA1sl1.sedo.com hostmaster.sedo.de

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (sl1.sedo.com, sl2.sedo.com)

Analysis

IP Addresses

jpre.com resolves to one IP address: 91.195.241.232.

xumz.com, womansassociation.de, veroz.de and two other host names share IP numbers with jpre.com.

Name Servers

DNS delegation for jpre.com points to two name servers: sl1.sedo.com and sl2.sedo.com.

jpre.com uses the same name servers as several other domains — among them 146.149.thedoghouse.eu, backend.atlassolution.de, mail.space-lab.eu and two more.

Each of sl1.sedo.com and sl2.sedo.com has one IP address: sl1.sedo.com uses 91.195.240.173 and sl2.sedo.com uses 91.195.241.173.

Mail Servers

Mail for jpre.com is handled by a single mail server, localhost.

jpre.com uses an identical mail server configuration to several other domains — among them he.to, cthouse4u.com, mx.bizius.com and two more.