automaticresponse.com - dns.ninja

`automaticresponse.com`

DNSSEC	⚠️ Not signed
A	2606:4700:20::681a:be^{🇺🇸 Cloudflare2606:4700:20::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:20::681a:1be^{🇺🇸 Cloudflare2606:4700:20::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:20::ac43:4528^{🇺🇸 Cloudflare2606:4700:20::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.26.0.190^{Cloudflare104.26.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.26.1.190^{Cloudflare104.26.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.69.40^{🇺🇸 Cloudflare172.67.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`meg.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3ac4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`meg.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0c4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`meg.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20c4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`meg.ns.cloudflare.com`
		A	108.162.192.196^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`meg.ns.cloudflare.com`
		A	172.64.32.196^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`meg.ns.cloudflare.com`
		A	173.245.58.196^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`meg.ns.cloudflare.com`
NS	`sid.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b8f^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sid.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c18f^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`sid.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:218f^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`sid.ns.cloudflare.com`
		A	108.162.193.143^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sid.ns.cloudflare.com`
		A	172.64.33.143^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sid.ns.cloudflare.com`
		A	173.245.59.143^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sid.ns.cloudflare.com`
MX	`mx1-us1.ppe-hosted.com` ⭐
		A	67.231.154.162^{🇺🇸 Proofpoint67.231.154.0/24 Inc.}
			PTR	`mx1-us1.ppe-hosted.com`
		A	148.163.129.50^{🇺🇸 AS13916148.163.129.0/24 Proofpoint Inc.}
			PTR	`mx1-us1.ppe-hosted.com`
MX	`mx2-us1.ppe-hosted.com`⁽²⁰⁾
		A	67.231.154.163^{🇺🇸 Proofpoint67.231.154.0/24 Inc.}
			PTR	`mx2-us1.ppe-hosted.com`
		A	148.163.129.51^{🇺🇸 AS13916148.163.129.0/24 Proofpoint Inc.}
			PTR	`mx2-us1.ppe-hosted.com`
TXT	`fe4lg6ua9c1qidf3k44jlkj1kr`
TXT	`ppe-0adf0960b8b5e9e35324a6ce7fea73b2ce9a8fab`
TXT	`v=spf1 include:spf.protection.outlook.com include:spf.mandrillapp.com include...`
HTTPS	HTTP/2 ✓ hints match
		IPv4 hints	104.26.0.190, 104.26.1.190, 172.67.69.40
		IPv6 hints	2606:4700:20::681a:be, 2606:4700:20::681a:1be, 2606:4700:20::ac43:4528
SOA	`meg.ns.cloudflare.com`dns@cloudflare.com serial=2409747679

`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=1785590917

WOT: UNKNOWN (61/100)

Subdomains

ns3.automaticresponse.com

www.automaticresponse.com

ns4.automaticresponse.com

ns2.automaticresponse.com

ns1.automaticresponse.com

mail.automaticresponse.com

hosted.automaticresponse.com

Same first word

automaticresponse.com

DNS History

21 records (10 active, 11 former)

●NSmeg.ns.cloudflare.com2026-02-15 → 2026-08-01 · 3 obs

○ 2017-11-23 04:15:14
● 2026-02-15 20:39:00
● 2026-08-01 13:55:26

○NSns1.automaticresponse.com2015-06-21 → 2016-01-24 · 4 obs

● 2015-06-21 16:17:58
● 2016-01-24 07:21:30
○ 2016-04-12 09:50:14
○ 2026-08-01 13:55:26

○NSns2.automaticresponse.com2015-06-21 → 2016-01-24 · 4 obs

● 2015-06-21 16:17:58
● 2016-01-24 07:21:30
○ 2016-04-12 09:50:14
○ 2026-08-01 13:55:26

○NSns3.automaticresponse.com2016-04-12 → 2017-11-23 · 5 obs

○ 2016-01-24 07:21:30
● 2016-04-12 09:50:14
● 2017-11-23 04:15:14
○ 2026-02-15 20:39:00
○ 2026-08-01 13:55:26

○NSns4.automaticresponse.com2016-04-12 → 2017-11-23 · 5 obs

○ 2016-01-24 07:21:30
● 2016-04-12 09:50:14
● 2017-11-23 04:15:14
○ 2026-02-15 20:39:00
○ 2026-08-01 13:55:26

●NSsid.ns.cloudflare.com2026-02-15 → 2026-08-01 · 3 obs

○ 2017-11-23 04:15:14
● 2026-02-15 20:39:00
● 2026-08-01 13:55:26

○MXautomaticresponse.com.1.0001.arsmtp.com2017-11-23 → 2017-11-23 · 4 obs

○ 2016-12-08 23:16:16
● 2017-11-23 04:15:14
○ 2026-02-15 20:39:00
○ 2026-08-01 13:55:26

○MXautomaticresponse.com.2.0001.arsmtp.com2017-11-23 → 2017-11-23 · 4 obs

○ 2016-12-08 23:16:16
● 2017-11-23 04:15:14
○ 2026-02-15 20:39:00
○ 2026-08-01 13:55:26

○MXmail.automaticresponse.com2015-06-21 → 2016-04-12 · 4 obs

● 2015-06-21 16:17:58
● 2016-04-12 09:50:14
○ 2016-12-08 23:16:16
○ 2026-08-01 13:55:26

○MXmail01.grupo-sms-usa.com2016-12-08 → 2016-12-08 · 4 obs

○ 2016-04-12 09:50:14
● 2016-12-08 23:16:16
○ 2017-11-23 04:15:14
○ 2026-08-01 13:55:26

○MXmail02.grupo-sms-usa.com2016-12-08 → 2016-12-08 · 4 obs

○ 2016-04-12 09:50:14
● 2016-12-08 23:16:16
○ 2017-11-23 04:15:14
○ 2026-08-01 13:55:26

●MXmx1-us1.ppe-hosted.com2026-02-15 → 2026-08-01 · 3 obs

○ 2017-11-23 04:15:14
● 2026-02-15 20:39:00
● 2026-08-01 13:55:26

●MXmx2-us1.ppe-hosted.com2026-02-15 → 2026-08-01 · 3 obs

○ 2017-11-23 04:15:14
● 2026-02-15 20:39:00
● 2026-08-01 13:55:26

●A104.26.0.1902026-02-15 → 2026-08-01 · 3 obs

○ 2017-11-23 04:15:14
● 2026-02-15 20:39:00
● 2026-08-01 13:55:26

●A104.26.1.1902026-02-15 → 2026-08-01 · 3 obs

○ 2017-11-23 04:15:14
● 2026-02-15 20:39:00
● 2026-08-01 13:55:26

●A172.67.69.402026-02-15 → 2026-08-01 · 3 obs

○ 2017-11-23 04:15:14
● 2026-02-15 20:39:00
● 2026-08-01 13:55:26

○A199.255.24.1602015-06-21 → 2016-04-12 · 4 obs

● 2015-06-21 16:17:58
● 2016-04-12 09:50:14
○ 2016-12-08 23:16:16
○ 2026-08-01 13:55:26

○A208.82.141.1512016-12-08 → 2017-11-23 · 5 obs

○ 2016-04-12 09:50:14
● 2016-12-08 23:16:16
● 2017-11-23 04:15:14
○ 2026-02-15 20:39:00
○ 2026-08-01 13:55:26

●A2606:4700:20::681a:1be2026-02-15 → 2026-08-01 · 3 obs

○ 2017-11-23 04:15:14
● 2026-02-15 20:39:00
● 2026-08-01 13:55:26

●A2606:4700:20::681a:be2026-02-15 → 2026-08-01 · 3 obs

○ 2017-11-23 04:15:14
● 2026-02-15 20:39:00
● 2026-08-01 13:55:26

●A2606:4700:20::ac43:45282026-02-15 → 2026-08-01 · 3 obs

○ 2017-11-23 04:15:14
● 2026-02-15 20:39:00
● 2026-08-01 13:55:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
automaticresponse.com	sid.ns.cloudflare.com, meg.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.193.143

NS records: sid.ns.cloudflare.com, meg.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for automaticresponse.com (unsigned zone)

⏱️ Timing

Total: 177ms | Queries: -

📄 Records

Type	Count	Sample Data
A	3	`104.26.1.190, 172.67.69.40...`
AAAA	3	`2606:4700:20::ac43:4528, 2606:4700:20::681a:be...`
NS	2	`meg.ns.cloudflare.com, sid.ns.cloudflare.com`
MX	2	`mx1-us1.ppe-hosted.com (pri: 10), mx2-us1.ppe-hosted.com (pri: 20)`
TXT	3	`fe4lg6ua9c1qidf3k44jlkj1kr, ppe-0adf0960b8b5e9e35324a6ce7fea73b2ce9a...`
HTTPS	1	`{"priority":1,"target":".","alpn":["h2"]`
SOA	1	`meg.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 12

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

Analysis

Hierarchy

The host names ns3.automaticresponse.com, www.automaticresponse.com, ns4.automaticresponse.com, ns2.automaticresponse.com and ns1.automaticresponse.com — among a few others — fall under the parent domain automaticresponse.com.

IP Addresses

automaticresponse.com directs to 6 IP numbers: 104.26.0.190, 104.26.1.190, 172.67.69.40 and 3 other.

Two other host names, along with trempswd.tremglobal.com, gravatar.loli.net.cdn.cloudflare.net and prometheus.5-15globalenergy.it, also share IP numbers with automaticresponse.com.

Name Servers

automaticresponse.com uses two name servers for its delegation: meg.ns.cloudflare.com and sid.ns.cloudflare.com.

automaticresponse.com shares its NS records with other domains, for example frontdoor.im, milk-sa.pages.dev, sagdas.com and two others.

At least some of automaticresponse.com's name servers are shared with other domains, for example blogsland.net, mapneticly-no.com, kmyxzl.com and two more.

It is common for these name servers to be used in conjunction with the name servers dexter.ns.cloudflare.com, aiden.ns.cloudflare.com and beth.ns.cloudflare.com.

DNS names with 6 IP addresses:

Hostname meg.ns.cloudflare.com directs to 108.162.192.196, 172.64.32.196 and 173.245.58.196 along with 3 other IP addresses.

Hostname sid.ns.cloudflare.com directs to 108.162.193.143, 172.64.33.143 and 173.245.59.143 along with 3 other IP addresses.

Mail Servers

automaticresponse.com is served by two mail servers, mx1-us1.ppe-hosted.com and mx2-us1.ppe-hosted.com.

Among the domains sharing a mail server setup with automaticresponse.com are primoticketing.com, ci.san-marino.ca.us, anchoragecc.com and two others.

There is at least a partial MX overlap between automaticresponse.com and other domains, including arbiteria.com, seniordiscoverytours.ca, hilgartnerhealth.com and two others.

The two host names mx1-us1.ppe-hosted.com and mx2-us1.ppe-hosted.com each have a pair of IP addresses: mx1-us1.ppe-hosted.com has 67.231.154.162 and 148.163.129.50, and mx2-us1.ppe-hosted.com has 67.231.154.163 and 148.163.129.51.