`coreincident.com`

DNSSEC	⚠️ Not signed
A	3.170.19.14^{🇺🇸 Amazon3.170.19.0/24}
		PTR	`server-3-170-19-14.iad61.r.cloudfront.net`
A	3.170.19.85^{🇺🇸 Amazon3.170.19.0/24}
A	3.170.19.108^{🇺🇸 Amazon3.170.19.0/24}
A	3.170.19.129^{🇺🇸 Amazon3.170.19.0/24}
NS	`ns-1411.awsdns-48.org` ⭐
		A	2600:9000:5305:8300::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1411.awsdns-48.org`
		A	205.251.197.131^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1411.awsdns-48.org`
NS	`ns-1688.awsdns-19.co.uk`
		A	2600:9000:5306:9800::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1688.awsdns-19.co.uk`
		A	205.251.198.152^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1688.awsdns-19.co.uk`
NS	`ns-351.awsdns-43.com`
		A	2600:9000:5301:5f00::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-351.awsdns-43.com`
		A	205.251.193.95^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-351.awsdns-43.com`
NS	`ns-989.awsdns-59.net`
		A	2600:9000:5303:dd00::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-989.awsdns-59.net`
		A	205.251.195.221^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-989.awsdns-59.net`
SOA	`ns-1411.awsdns-48.org`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

Same first word

coreincident.com

DNS History

12 records (8 active, 4 former)

●NSns-1411.awsdns-48.org2026-02-28 → 2026-03-01 · 2 obs

● 2026-02-28 11:11:56
● 2026-03-01 03:40:02

●NSns-1688.awsdns-19.co.uk2026-02-28 → 2026-03-01 · 2 obs

● 2026-02-28 11:11:56
● 2026-03-01 03:40:02

●NSns-351.awsdns-43.com2026-02-28 → 2026-03-01 · 2 obs

● 2026-02-28 11:11:56
● 2026-03-01 03:40:02

●NSns-989.awsdns-59.net2026-02-28 → 2026-03-01 · 2 obs

● 2026-02-28 11:11:56
● 2026-03-01 03:40:02

●A3.170.19.1082026-02-28 → 2026-03-01 · 3 obs

● 2026-02-28 11:11:56
○ 2026-03-01 01:53:46
● 2026-03-01 03:40:02

●A3.170.19.1292026-02-28 → 2026-03-01 · 3 obs

● 2026-02-28 11:11:56
○ 2026-03-01 01:53:46
● 2026-03-01 03:40:02

●A3.170.19.142026-02-28 → 2026-03-01 · 3 obs

● 2026-02-28 11:11:56
○ 2026-03-01 01:53:46
● 2026-03-01 03:40:02

●A3.170.19.852026-02-28 → 2026-03-01 · 3 obs

● 2026-02-28 11:11:56
○ 2026-03-01 01:53:46
● 2026-03-01 03:40:02

○A99.84.41.1222026-03-01 → 2026-03-01 · 3 obs

○ 2026-02-28 11:11:56
● 2026-03-01 01:53:46
○ 2026-03-01 03:40:02

○A99.84.41.1232026-03-01 → 2026-03-01 · 3 obs

○ 2026-02-28 11:11:56
● 2026-03-01 01:53:46
○ 2026-03-01 03:40:02

○A99.84.41.242026-03-01 → 2026-03-01 · 3 obs

○ 2026-02-28 11:11:56
● 2026-03-01 01:53:46
○ 2026-03-01 03:40:02

○A99.84.41.842026-03-01 → 2026-03-01 · 3 obs

○ 2026-02-28 11:11:56
● 2026-03-01 01:53:46
○ 2026-03-01 03:40:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net...	-
coreincident.com	ns-351.awsdns-43.com, ns-989.awsdns-59.net, ns-1688.awsdns-19.co.uk, ns-1411.awsdns-48.org	1 record

✅ Authoritative Response

Server: 205.251.193.95

NS records: ns-351.awsdns-43.com, ns-989.awsdns-59.net, ns-1688.awsdns-19.co.uk, ns-1411.awsdns-48.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for coreincident.com (unsigned zone)

⏱️ Timing

Total: 205ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`3.170.19.129, 3.170.19.14...`
NS	4	`ns-1411.awsdns-48.org, ns-1688.awsdns-19.co.uk...`
SOA	1	`ns-1411.awsdns-48.org awsdns-hostmaster.`

📌 Glue Records Collected

Total: 1

Out-of-bailiwick: 1 (ns-351.awsdns-43.com)

Analysis

IP Addresses

coreincident.com resolves to four IP numbers: 3.170.19.14, 3.170.19.85, 3.170.19.108 and 3.170.19.129.

other host names for instance play9round.com, drove.co.il, api.sandbox.dapx.digital, 36game2.com and cirquedusoleilhartford.com share IP numbers with coreincident.com.

Name Servers

coreincident.com is delegated to four name servers: ns-351.awsdns-43.com, ns-989.awsdns-59.net, ns-1411.awsdns-48.org and ns-1688.awsdns-19.co.uk.

coreincident.com at least partially shares name servers with other domains, for instance crs-corp.com, alyssa.one, lalife.net, 1wallstreet.com and donqdmhih090v.cloudfront.net.

These name servers are commonly used with ns-1541.awsdns-00.co.uk, ns-815.awsdns-37.net, ns-1438.awsdns-51.org, ns81.music-name-servers.com, ns82.music-name-servers.com, ns83.music-name-servers.com, ns84.music-name-servers.com and ns-319.awsdns-39.com.

Host names with two IP numbers:

Host name ns-351.awsdns-43.com points to: 2600:9000:5301:5f00::1 and 205.251.193.95.

Host name ns-989.awsdns-59.net points to: 2600:9000:5303:dd00::1 and 205.251.195.221.

Host name ns-1411.awsdns-48.org points to: 2600:9000:5305:8300::1 and 205.251.197.131.

Host name ns-1688.awsdns-19.co.uk points to: 2600:9000:5306:9800::1 and 205.251.198.152.

coreincident.com - robtex.com