`incidentcare.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns1.afternic.com` ⭐
		A	2603:5:2126::45^{🇺🇸 GODADDY-DNS2603:5:2120::/44}
			PTR	`ns1.afternic.com`
		A	97.74.98.69^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.afternic.com`
NS	`ns2.afternic.com`
		A	2603:5:2226::45^{🇺🇸 GODADDY-DNS2603:5:2220::/44}
			PTR	`ns2.afternic.com`
		A	173.201.66.69^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.afternic.com`
TXT	`v=spf1 -all`
SOA	`ns1.afternic.com`dns@jomax.net 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=1774647827

Same first word

incidentcare.com

DNS History

15 records (4 active, 11 former)

○NSns.123-reg.co.uk2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 05:04:32
○ 2015-06-06 14:47:32
○ 2026-03-27 21:52:02

○NSns.hosteurope.com2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 05:04:32
○ 2015-06-06 14:47:32
○ 2026-03-27 21:52:02

●NSns1.afternic.com2026-03-02 → 2026-03-27 · 3 obs

○ 2017-09-12 01:51:38
● 2026-03-02 10:02:16
● 2026-03-27 21:52:02

○NSns1.logical.net2015-06-06 → 2017-09-12 · 5 obs

○ 2008-03-08 05:04:32
● 2015-06-06 14:47:32
● 2017-09-12 01:51:38
○ 2026-03-02 10:02:16
○ 2026-03-27 21:52:02

○NSns2.123-reg.co.uk2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 05:04:32
○ 2015-06-06 14:47:32
○ 2026-03-27 21:52:02

●NSns2.afternic.com2026-03-02 → 2026-03-27 · 3 obs

○ 2017-09-12 01:51:38
● 2026-03-02 10:02:16
● 2026-03-27 21:52:02

○NSns2.hosteurope.com2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 05:04:32
○ 2015-06-06 14:47:32
○ 2026-03-27 21:52:02

○NSns2.logical.net2015-06-06 → 2017-09-12 · 5 obs

○ 2008-03-08 05:04:32
● 2015-06-06 14:47:32
● 2017-09-12 01:51:38
○ 2026-03-02 10:02:16
○ 2026-03-27 21:52:02

○NSns3.logical.net2015-06-06 → 2017-09-12 · 5 obs

○ 2008-03-08 05:04:32
● 2015-06-06 14:47:32
● 2017-09-12 01:51:38
○ 2026-03-02 10:02:16
○ 2026-03-27 21:52:02

○MXmx0.123-reg.co.uk2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 05:04:32
○ 2015-06-06 14:47:32
○ 2026-03-27 21:52:02

○MXmx1.123-reg.co.uk2008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 05:04:32
○ 2015-06-06 14:47:32
○ 2026-03-27 21:52:02

●A13.248.169.482026-03-02 → 2026-03-27 · 3 obs

○ 2017-09-12 01:51:38
● 2026-03-02 10:02:16
● 2026-03-27 21:52:02

○A195.224.48.742008-03-08 → 2008-03-08 · 3 obs

● 2008-03-08 05:04:32
○ 2015-06-06 14:47:32
○ 2026-03-27 21:52:02

○A209.23.117.52015-06-06 → 2017-09-12 · 5 obs

○ 2008-03-08 05:04:32
● 2015-06-06 14:47:32
● 2017-09-12 01:51:38
○ 2026-03-02 10:02:16
○ 2026-03-27 21:52:02

●A76.223.54.1462026-03-02 → 2026-03-27 · 3 obs

○ 2017-09-12 01:51:38
● 2026-03-02 10:02:16
● 2026-03-27 21:52:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
incidentcare.com	ns1.afternic.com, ns2.afternic.com	4 records

✅ Authoritative Response

Server:97.74.98.69

NS records: ns1.afternic.com, ns2.afternic.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for incidentcare.com (unsigned zone)

⏱️ Timing

Total: 102ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.54.146, 13.248.169.48`
NS	2	`ns1.afternic.com, ns2.afternic.com`
MX	1	`. (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.afternic.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)

Analysis

IP Addresses

incidentcare.com resolves to two IP numbers: 13.248.169.48 and 76.223.54.146.

other host names including hostmaster.reformedbaptistchurch.com, splube.com, meetrichman.com, boxweiler.com and zuqiuxinhuangguanwang.qqpower.com share IP numbers with incidentcare.com.

Name Servers

incidentcare.com is delegated to two name servers ns1.afternic.com and ns2.afternic.com.

incidentcare.com shares the same name server setup as other domains, for instance transpayments.com, bloomingtrees.com, ramsgroup.com, debtforge.com and host-217-77-0-164.ptr.7global.com.

incidentcare.com at least partially shares name servers with other domains, for instance c7p.com, subite.com, brilliantcoding.com, qsuj.com and socon.co.uk.

These name servers are commonly used with verification-ag3xtxqjhqhiyarqdrht2l.ns101.verify.hn, verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn and verification-emph5yqtrtvjaianaqdbfd.ns101.verify.hn.

Host names with two IP numbers:

The host name ns1.afternic.com points to 2603:5:2126::45 and 97.74.98.69; the host name ns2.afternic.com points to 2603:5:2226::45 and 173.201.66.69.

incidentcare.com - robtex.com