botrespond.com - dns.ninja

`botrespond.com`

DNSSEC	⚠️ Not signed
A	20.118.48.15^{🇺🇸 Microsoft20.64.0.0/10}
NS	`ns31.domaincontrol.com` ⭐
		A	2603:5:2191::10^{🇺🇸 GODADDY-DNS2603:5:2190::/44}
			PTR	`ns31.domaincontrol.com`
		A	97.74.105.16^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns31.domaincontrol.com`
NS	`ns32.domaincontrol.com`
		A	2603:5:2291::10^{🇺🇸 GODADDY-DNS2603:5:2290::/44}
			PTR	`ns32.domaincontrol.com`
		A	173.201.73.16^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns32.domaincontrol.com`
MX	`botrespond-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00401.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch5pr02cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch5pr02cu00307.inbound.protection.outlook.com`
		A	2a01:111:f403:f907::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm1pr04cu00201.inbound.protection.outlook.com`
		A	52.101.11.3^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr0501cu00103.inbound.protection.outlook.com`
		A	52.101.11.15^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr02cu00207.inbound.protection.outlook.com`
		A	52.101.41.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01600.inbound.protection.outlook.com`
		A	52.101.41.54^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj2pr05cu00506.inbound.protection.outlook.com`
SOA	`ns31.domaincontrol.com`dns@jomax.net 2026-06-01 #2

	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=1782375025

botrespond.com

5 records (4 active, 1 former)

●NSns31.domaincontrol.com2016-12-20 → 2026-06-25 · 2 obs

● 2016-12-20 00:19:22
● 2026-06-25 08:11:22

●NSns32.domaincontrol.com2016-12-20 → 2026-06-25 · 2 obs

● 2016-12-20 00:19:22
● 2026-06-25 08:11:22

●MXbotrespond-com.mail.protection.outlook.com2016-12-20 → 2026-06-25 · 2 obs

● 2016-12-20 00:19:22
● 2026-06-25 08:11:22

●A20.118.48.152026-04-02 → 2026-06-25 · 3 obs

○ 2017-10-04 22:15:28
● 2026-04-02 03:55:32
● 2026-06-25 08:11:22

○A23.101.118.1452016-12-20 → 2017-10-04 · 4 obs

● 2016-12-20 00:19:22
● 2017-10-04 22:15:28
○ 2026-04-02 03:55:32
○ 2026-06-25 08:11:22

Zone	Nameservers	Glue
com	b.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net, m.gtld-servers.net...	-
botrespond.com	ns31.domaincontrol.com, ns32.domaincontrol.com	4 records

Server:173.201.73.16

NS records: ns31.domaincontrol.com, ns32.domaincontrol.com

⚠️ Insecure (no DNSSEC)

No DS record for botrespond.com (unsigned zone)

Total: 362ms | Queries: -

Type	Count	Sample Data
A	1	`20.118.48.15`
NS	2	`ns31.domaincontrol.com, ns32.domaincontrol.com`
MX	1	`botrespond-com.mail.protection.outlook.c`
SOA	1	`ns31.domaincontrol.com dns.jomax.net`

Total: 4

Out-of-bailiwick: 4 (ns31.domaincontrol.com, ns31.domaincontrol.com, ns32.domaincontrol.com...)

botrespond.com has exactly one IP address — 20.118.48.15.

clarityads.com, radianse.io, waws-prod-dm1-349-5d86.centralus.cloudapp.azure.com plus two other host names have IP numbers in common with botrespond.com.

botrespond.com is delegated to two name servers: ns31.domaincontrol.com and ns32.domaincontrol.com.

The name server configuration of botrespond.com is shared with other domains, for instance triple(0x736578)o.com, tyroid.com, vlex.mobi and two others.