incidentradar.app - robtex.com
incidentradar.app
| DNSSEC | ⚠️ Not signed | ||||||
| A | 216.150.1.193🇨🇦 Amazon216.150.1.0/24 EC2 Prefix | ||||||
| A | 216.150.16.1🇨🇦 Amazon216.150.16.0/24 EC2 Prefix | ||||||
| NS | ns1.vercel-dns.com ⭐ | ||||||
| A | 2620:4d:4000:6259:7:13:0:1🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1 | ||||||
| PTR | dns1.p13.nsone.net | ||||||
| A | 198.51.44.13🇺🇸 NSONE198.51.44.0/24 | ||||||
| PTR | dns1.p13.nsone.net | ||||||
| NS | ns2.vercel-dns.com | ||||||
| A | 2a00:edc0:6259:7:13::2🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2 | ||||||
| PTR | dns2.p13.nsone.net | ||||||
| A | 198.51.45.13🇺🇸 NSONE198.51.45.0/24 | ||||||
| PTR | dns2.p13.nsone.net | ||||||
| SOA | ns1.vercel-dns.comhostmaster@nsone.net serial=1734126682 | ||||||
app
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=101427 | ||||||
Same first word
incidentradar.app |
Similar names
DNS History
8 records (4 active, 4 former)
●NSns1.vercel-dns.com2026-07-14 → 2026-08-04 · 2 obs
● 2026-08-04 20:51:50
●NSns2.vercel-dns.com2026-07-14 → 2026-08-04 · 2 obs
● 2026-08-04 20:51:50
○A216.150.1.12026-07-14 → 2026-07-15 · 4 obs
○ 2026-07-14 22:24:04
● 2026-07-15 06:54:16
○ 2026-08-04 20:51:50
○A216.150.1.1292026-07-14 → 2026-07-15 · 5 obs
● 2026-07-14 22:24:04
○ 2026-07-14 22:59:56
● 2026-07-15 06:54:16
○ 2026-08-04 20:51:50
●A216.150.1.1932026-07-14 → 2026-08-04 · 3 obs
○ 2026-07-14 22:24:04
● 2026-08-04 20:51:50
●A216.150.16.12026-07-14 → 2026-08-04 · 4 obs
● 2026-07-14 22:59:56
○ 2026-07-15 06:54:16
● 2026-08-04 20:51:50
○A216.150.16.1932026-07-14 → 2026-07-14 · 4 obs
● 2026-07-14 22:24:04
○ 2026-07-14 22:59:56
○ 2026-08-04 20:51:50
○A216.150.16.652026-07-14 → 2026-07-14 · 4 obs
● 2026-07-14 22:59:56
○ 2026-07-15 06:54:16
○ 2026-08-04 20:51:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| app | ns-tld2.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com... | - |
| incidentradar.app | ns1.vercel-dns.com, ns2.vercel-dns.com | - |
✅ Authoritative Response
Server:198.51.45.13
NS records: ns1.vercel-dns.com, ns2.vercel-dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for incidentradar.app (unsigned zone)
⏱️ Timing
Total: 636ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 216.150.1.129, 216.150.16.129 |
| NS | 2 | ns1.vercel-dns.com, ns2.vercel-dns.com |
| SOA | 1 | ns1.vercel-dns.com hostmaster.nsone.net |
Analysis
IP Addresses
incidentradar.app has two IP addresses: 216.150.1.193 and 216.150.16.1
gatesofolimpus-az.com, ns1.mcdsystems.co.uk, starlight-express.de plus two other host names have IP numbers in common with incidentradar.app.
Name Servers
Two name servers handle the delegation for incidentradar.app: ns1.vercel-dns.com and ns2.vercel-dns.com.
The name server configuration of incidentradar.app is shared with other domains, for instance listacasinosonlinept.com, unclassified.community, winme.org and two others.
There is at least partial name server overlap between incidentradar.app and other domains — cheese.singles, promptelixir.online, thewatchsociety.com and two more among them.
ns1.vercel-dns.com and ns2.vercel-dns.com both carry two IP addresses. The A records for ns1.vercel-dns.com are 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1; the A records for ns2.vercel-dns.com are 198.51.45.13 and 2a00:edc0:6259:7:13::2.