chasefleming.net - robtex.com
chasefleming.net
net
| 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=1786949334 | ||||||
Same first word
Similar names
DNS History
6 records (6 active, 0 former)
●NSns0087.secondary.cloudflare.com2026-08-12 → 2026-08-17 · 3 obs
● 2026-08-12 03:14:30
● 2026-08-17 06:54:02
●NSns0134.secondary.cloudflare.com2026-08-12 → 2026-08-17 · 3 obs
● 2026-08-12 03:14:30
● 2026-08-17 06:54:02
●NSns05.jpmorganchase.com2015-06-19 → 2026-08-17 · 2 obs
● 2026-08-17 06:54:02
●NSns06.jpmorganchase.com2015-06-19 → 2026-08-17 · 2 obs
● 2026-08-17 06:54:02
●NSns1.jpmorganchase.com2015-06-19 → 2026-08-17 · 2 obs
● 2026-08-17 06:54:02
●NSns2.jpmorganchase.com2015-06-19 → 2026-08-17 · 2 obs
● 2026-08-17 06:54:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, d.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net... | - |
| chasefleming.net | ns1.jpmorganchase.com, ns2.jpmorganchase.com, ns05.jpmorganchase.com, ns06.jpmorganchase.com | - |
✅ Authoritative Response
Server:146.143.131.130
NS records: ns1.jpmorganchase.com, ns2.jpmorganchase.com, ns05.jpmorganchase.com, ns06.jpmorganchase.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for chasefleming.net (unsigned zone)
⏱️ Timing
Total: 2680ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 6 | ns0087.secondary.cloudflare.com, ns2.jpmorganchase.com... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.jpmorganchase.com hostmaster.jpmchas |
Analysis
Name Servers
chasefleming.net has 6 name servers — ns05.jpmorganchase.com, ns06.jpmorganchase.com, ns1.jpmorganchase.com and 3 others.
chasefleming.net has at least partial name server overlap with other domains, such as jpmacademy.co.uk, progressivesoftwarepayments.com, chasepaymobile.info and two others.
ns2.jpmorganchase.com, ns0037.secondary.cloudflare.com and ns0246.secondary.cloudflare.com — plus 4 other name servers — are commonly paired with these name servers.
Host names with two IP numbers:
ns0087.secondary.cloudflare.com resolves to 162.159.32.88 and 2606:4700:51::a29f:2058.
ns0134.secondary.cloudflare.com resolves to 162.159.33.9 and 2606:4700:59::a29f:2109.
Host names pointing to a single IP address:
ns05.jpmorganchase.com resolves to 146.143.195.130.
ns06.jpmorganchase.com resolves to 146.143.131.130.
ns1.jpmorganchase.com resolves to 146.143.67.130.
ns2.jpmorganchase.com resolves to 146.143.3.130.