`incidentview.com`

DNSSEC	⚠️ Not signed
NS	`ns-313.awsdns-39.com` ⭐
		A	2600:9000:5301:3900::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-313.awsdns-39.com`
		A	205.251.193.57^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-313.awsdns-39.com`
NS	`ns-1224.awsdns-25.org`
		A	2600:9000:5304:c800::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1224.awsdns-25.org`
		A	205.251.196.200^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1224.awsdns-25.org`
NS	`ns-1936.awsdns-50.co.uk`
		A	2600:9000:5307:9000::1^{🇺🇸 Amazon2600:9000:5307::/48 - CloudFront}
			PTR	`ns-1936.awsdns-50.co.uk`
		A	205.251.199.144^{🇺🇸 Amazon205.251.199.0/24 prefix}
			PTR	`ns-1936.awsdns-50.co.uk`
NS	`ns-608.awsdns-12.net`
		A	2600:9000:5302:6000::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-608.awsdns-12.net`
		A	205.251.194.96^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-608.awsdns-12.net`
TXT	`v=spf1 include:emailsrvr.com ~all`
SOA	`ns-313.awsdns-39.com`awsdns-hostmaster@amazon.com serial=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.net`nstld@verisign-grs.com serial=1771291435

DNS History

6 records (4 active, 2 former)

●NSns-1224.awsdns-25.org2015-08-09 → 2026-03-05 · 2 obs

● 2015-08-09 03:42:10
● 2026-03-05 09:00:12

●NSns-1936.awsdns-50.co.uk2015-08-09 → 2026-03-05 · 2 obs

● 2015-08-09 03:42:10
● 2026-03-05 09:00:12

●NSns-313.awsdns-39.com2015-08-09 → 2026-03-05 · 2 obs

● 2015-08-09 03:42:10
● 2026-03-05 09:00:12

●NSns-608.awsdns-12.net2015-08-09 → 2026-03-05 · 2 obs

● 2015-08-09 03:42:10
● 2026-03-05 09:00:12

○A69.195.82.2072017-04-18 → 2017-04-18 · 3 obs

○ 2016-10-17 04:59:12
● 2017-04-18 19:56:30
○ 2026-03-05 09:00:12

○A74.220.215.692015-08-09 → 2016-10-17 · 4 obs

● 2015-08-09 03:42:10
● 2016-10-17 04:59:12
○ 2017-04-18 19:56:30
○ 2026-03-05 09:00:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
incidentview.com	ns-608.awsdns-12.net, ns-313.awsdns-39.com, ns-1224.awsdns-25.org, ns-1936.awsdns-50.co.uk	1 record

✅ Authoritative Response

Server: 205.251.199.144

NS records: ns-608.awsdns-12.net, ns-313.awsdns-39.com, ns-1224.awsdns-25.org, ns-1936.awsdns-50.co.uk

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for incidentview.com (unsigned zone)

⏱️ Timing

Total: 433ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1224.awsdns-25.org, ns-1936.awsdns-50.co.uk...`
TXT	1	`v=spf1 include:emailsrvr.com ~all`
SOA	1	`ns-313.awsdns-39.com awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 1

Out-of-bailiwick: 1 (ns-313.awsdns-39.com)

Analysis

Name Servers

incidentview.com is delegated to four name servers: ns-313.awsdns-39.com, ns-608.awsdns-12.net, ns-1224.awsdns-25.org and ns-1936.awsdns-50.co.uk.

At least part of the name servers for incidentview.com are shared with other domains, for instance d179e0pedj0ox1.cloudfront.net, oneearthdesigns.org, elasticloadbalancing.ap-south-1.amazonaws.com, finpage.net and johnston.works.

Host names with two IP numbers:

ns-313.awsdns-39.com points to: 2600:9000:5301:3900::1 and 205.251.193.57

ns-608.awsdns-12.net points to: 2600:9000:5302:6000::1 and 205.251.194.96

ns-1224.awsdns-25.org points to: 2600:9000:5304:c800::1 and 205.251.196.200

ns-1936.awsdns-50.co.uk points to: 2600:9000:5307:9000::1 and 205.251.199.144

incidentview.com - robtex.com