jpsergent.com - robtex.com
jpsergent.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=1771291435 | ||||||
Subdomains
Same first word
jpsergent.com |
DNS History
8 records (2 active, 6 former)
●NSalice.ns.cloudflare.com2026-03-14 → 2026-03-24 · 3 obs
● 2026-03-14 05:37:28
● 2026-03-24 01:27:42
○NSns1.jpsergent.com2015-05-21 → 2017-03-18 · 4 obs
● 2017-03-18 14:20:22
○ 2026-03-14 05:37:28
○ 2026-03-24 01:27:42
○NSns2.jpsergent.com2015-05-21 → 2017-03-18 · 4 obs
● 2017-03-18 14:20:22
○ 2026-03-14 05:37:28
○ 2026-03-24 01:27:42
○NSns3.jpsergent.com2015-05-21 → 2017-03-18 · 4 obs
● 2017-03-18 14:20:22
○ 2026-03-14 05:37:28
○ 2026-03-24 01:27:42
○NSns4.jpsergent.com2015-05-21 → 2017-03-18 · 4 obs
● 2017-03-18 14:20:22
○ 2026-03-14 05:37:28
○ 2026-03-24 01:27:42
●NSray.ns.cloudflare.com2026-03-14 → 2026-03-24 · 3 obs
● 2026-03-14 05:37:28
● 2026-03-24 01:27:42
○MXmail.jpsergent.com2015-05-21 → 2017-03-18 · 4 obs
● 2017-03-18 14:20:22
○ 2026-03-14 05:37:28
○ 2026-03-24 01:27:42
○A199.204.23.2042015-05-21 → 2017-03-18 · 4 obs
● 2017-03-18 14:20:22
○ 2026-03-14 05:37:28
○ 2026-03-24 01:27:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| jpsergent.com | ray.ns.cloudflare.com, alice.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.192.60
NS records: ray.ns.cloudflare.com, alice.ns.cloudflare.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 164ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | alice.ns.cloudflare.com, ray.ns.cloudflare.com |
| SOA | 1 | alice.ns.cloudflare.com dns.cloudflare.c |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (ray.ns.cloudflare.com, ray.ns.cloudflare.com, ray.ns.cloudflare.com...)
Analysis
Hierarchy
jpsergent.com is the parent of v1rt.jpsergent.com and ns1.jpsergent.com.
Name Servers
Two name servers alice.ns.cloudflare.com and ray.ns.cloudflare.com handle the delegation for jpsergent.com.
jpsergent.com shares the same name server setup as other domains, for instance e-visa.al, homecomputermuseum.nl, bujqesia.gov.al, jassengoose.nl and infermierepershqiperine.al.
jpsergent.com at least partially shares name servers with other domains, for instance 517py.com, bitcoinserver.net, lotterysambad.info, laamumaamendhoo.gov.mv and marcosortega.es.
These name servers are commonly used with josh.ns.cloudflare.com and yichun.ns.cloudflare.com.
Six IP addresses per host:
alice.ns.cloudflare.com points to 2606:4700:50::adf5:3a3c, 2803:f800:50::6ca2:c03c, 2a06:98c1:50::ac40:203c, 108.162.192.60, 172.64.32.60 and 173.245.58.60; ray.ns.cloudflare.com points to 2606:4700:58::adf5:3b8a, 2803:f800:50::6ca2:c18a, 2a06:98c1:50::ac40:218a, 108.162.193.138, 172.64.33.138 and 173.245.59.138