coreincident.com - robtex.com

coreincident.com

com

DNS History

8 records (8 active, 0 former)

NSns-1411.awsdns-48.orgns-1688.awsdns-19.co.ukns-351.awsdns-43.comns-989.awsdns-59.netA3.170.19.1083.170.19.1293.170.19.143.170.19.85
●NSns-1411.awsdns-48.org2026-02-28 β†’ 2026-02-28 Β· 2 obs
● 2026-02-28 11:11:56
● 2026-02-28 11:11:58
●NSns-1688.awsdns-19.co.uk2026-02-28 β†’ 2026-02-28 Β· 2 obs
● 2026-02-28 11:11:56
● 2026-02-28 11:11:58
●NSns-351.awsdns-43.com2026-02-28 β†’ 2026-02-28 Β· 2 obs
● 2026-02-28 11:11:56
● 2026-02-28 11:11:58
●NSns-989.awsdns-59.net2026-02-28 β†’ 2026-02-28 Β· 2 obs
● 2026-02-28 11:11:56
● 2026-02-28 11:11:58
●A3.170.19.1082026-02-28 β†’ 2026-02-28 Β· 2 obs
● 2026-02-28 11:11:56
● 2026-02-28 11:11:58
●A3.170.19.1292026-02-28 β†’ 2026-02-28 Β· 2 obs
● 2026-02-28 11:11:56
● 2026-02-28 11:11:58
●A3.170.19.142026-02-28 β†’ 2026-02-28 Β· 2 obs
● 2026-02-28 11:11:56
● 2026-02-28 11:11:58
●A3.170.19.852026-02-28 β†’ 2026-02-28 Β· 2 obs
● 2026-02-28 11:11:56
● 2026-02-28 11:11:58

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
coreincident.comns-351.awsdns-43.com, ns-989.awsdns-59.net, ns-1688.awsdns-19.co.uk, ns-1411.awsdns-48.org1 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: 272ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A43.170.19.108, 3.170.19.85...
NS4ns-1411.awsdns-48.org, ns-1688.awsdns-19.co.uk...
SOA1ns-1411.awsdns-48.org awsdns-hostmaster.

πŸ“Œ Glue Records Collected

Total: 1

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

AI analysis

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 ocedaa.com, drove.co.il, www.jacar.go.jp, dlcw7sl78mlf0.cloudfront.net and elitehhc.com share IP numbers with coreincident.com.

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.