`iresponding.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3033::6815:3b0c^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::ac43:a767^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.59.12^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.167.103^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`nolan.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c38^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nolan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c338^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`nolan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2338^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`nolan.ns.cloudflare.com`
		A	108.162.195.56^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nolan.ns.cloudflare.com`
		A	162.159.44.56^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nolan.ns.cloudflare.com`
		A	172.64.35.56^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nolan.ns.cloudflare.com`
NS	`sandy.ns.cloudflare.com`
		A	2606:4700:50::adf5:3adb^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0db^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`sandy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20db^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`sandy.ns.cloudflare.com`
		A	108.162.192.219^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
		A	172.64.32.219^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
		A	173.245.58.219^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
MX	`route1.mx.cloudflare.net` ⭐
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁴⁰⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁸⁵⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
TXT	`google-site-verification=hAnkrY798sFhWch9s938vwy5HFF5QypHqSKyUS4cxy0`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4	104.21.59.12, 172.67.167.103
		IPv6	2606:4700:3033::6815:3b0c, 2606:4700:3033::ac43:a767
SOA	`nolan.ns.cloudflare.com`dns@cloudflare.com serial=2398699252

`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

iresponding.com

Similar names

disponering.dk

DNS History

9 records (9 active, 0 former)

●NSnolan.ns.cloudflare.com2026-03-16 → 2026-03-24 · 2 obs

● 2026-03-16 10:47:28
● 2026-03-24 01:31:52

●NSsandy.ns.cloudflare.com2026-03-16 → 2026-03-24 · 2 obs

● 2026-03-16 10:47:28
● 2026-03-24 01:31:52

●MXroute1.mx.cloudflare.net2026-03-16 → 2026-03-24 · 2 obs

● 2026-03-16 10:47:28
● 2026-03-24 01:31:52

●MXroute2.mx.cloudflare.net2026-03-16 → 2026-03-24 · 2 obs

● 2026-03-16 10:47:28
● 2026-03-24 01:31:52

●MXroute3.mx.cloudflare.net2026-03-16 → 2026-03-24 · 2 obs

● 2026-03-16 10:47:28
● 2026-03-24 01:31:52

●A104.21.59.122026-03-16 → 2026-03-24 · 2 obs

● 2026-03-16 10:47:28
● 2026-03-24 01:31:52

●A172.67.167.1032026-03-16 → 2026-03-24 · 2 obs

● 2026-03-16 10:47:28
● 2026-03-24 01:31:52

●A2606:4700:3033::6815:3b0c2026-03-16 → 2026-03-24 · 2 obs

● 2026-03-16 10:47:28
● 2026-03-24 01:31:52

●A2606:4700:3033::ac43:a7672026-03-16 → 2026-03-24 · 2 obs

● 2026-03-16 10:47:28
● 2026-03-24 01:31:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net, d.gtld-servers.net...	-
iresponding.com	sandy.ns.cloudflare.com, nolan.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.56

NS records: sandy.ns.cloudflare.com, nolan.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for iresponding.com (unsigned zone)

⏱️ Timing

Total: 203ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.167.103, 104.21.59.12`
AAAA	2	`2606:4700:3033::6815:3b0c, 2606:4700:3033::ac43:a767`
NS	2	`nolan.ns.cloudflare.com, sandy.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 34), route3.mx.cloudflare.net (pri: 40)...`
TXT	2	`google-site-verification=hAnkrY798sFhWch, v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`nolan.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (sandy.ns.cloudflare.com, sandy.ns.cloudflare.com, sandy.ns.cloudflare.com...)

Analysis

IP Addresses

iresponding.com maps to four IP numbers: 2606:4700:3033::6815:3b0c, 2606:4700:3033::ac43:a767, 104.21.59.12 and 172.67.167.103.

Other host names, for instance kobetex.com, cheaperrates.org, www.whygo.net.cdn.cloudflare.net, diaosj.com and cr.myallplay-game.com share IP numbers with iresponding.com.

Name Servers

Two name servers nolan.ns.cloudflare.com and sandy.ns.cloudflare.com handle delegation for iresponding.com.

iresponding.com uses the same name server setup as other domains, for example nexyup.com, gwynmorfey.com, costen.net, webexpertise.us and tipmain.com.

iresponding.com partially shares name servers with other domains; examples include foreks.net, ns2.deneopreno.com, beverly.co.uk, pusakajerai.shop and kts-af.org.

These name servers are often used with the name servers jerry.ns.cloudflare.com and simone.ns.cloudflare.com.

Host names with six IP numbers: nolan.ns.cloudflare.com points to: 2606:4700:58::a29f:2c38, 2803:f800:50::6ca2:c338, 2a06:98c1:50::ac40:2338, 108.162.195.56, 162.159.44.56 and 172.64.35.56; sandy.ns.cloudflare.com points to: 2606:4700:50::adf5:3adb, 2803:f800:50::6ca2:c0db, 2a06:98c1:50::ac40:20db, 108.162.192.219, 172.64.32.219 and 173.245.58.219.

Mail Servers

iresponding.com is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

iresponding.com shares some mail servers with other domains, at least partially, such as riverlandcountrymusic.com, app-gala-games-official-l3.com, i365.me, fusang.me and jeffmatheson.ca.

Host names with six IP numbers:

route1.mx.cloudflare.net points to 2606:4700:f5::b, 2606:4700:f5::c, 2606:4700:f5::d, 162.159.205.11, 162.159.205.12 and 162.159.205.13.

route2.mx.cloudflare.net points to 2606:4700:f5::e, 2606:4700:f5::f, 2606:4700:f5::10, 162.159.205.17, 162.159.205.18 and 162.159.205.19.

route3.mx.cloudflare.net points to 2606:4700:f5::11, 2606:4700:f5::12, 2606:4700:f5::13, 162.159.205.23, 162.159.205.24 and 162.159.205.25.

iresponding.com - robtex.com

iresponding.com

com

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`iresponding.com`

`com`