`autoconcierge.co`

DNSSEC	⚠️ Not signed
A	52.34.165.215^{🇺🇸 Amazon52.32.0.0/14 EC2 PDX prefix}
		PTR	`ec2-52-34-165-215.us-west-2.compute.amazonaws.com`
NS	`ns23.domaincontrol.com` ⭐
		A	2603:5:2151::c^{🇺🇸 GODADDY-DNS2603:5:2150::/44}
			PTR	`ns23.domaincontrol.com`
		A	97.74.101.12^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns23.domaincontrol.com`
NS	`ns24.domaincontrol.com`
		A	2603:5:2251::c^{🇺🇸 GODADDY-DNS2603:5:2250::/44}
			PTR	`ns24.domaincontrol.com`
		A	173.201.69.12^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns24.domaincontrol.com`
MX	`autoconcierge-co.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c922::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr05cu00501.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr04cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mn2pr02cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:f90d::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr0501cu00200.inbound.protection.outlook.com`
		A	52.101.10.8^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn1pr04cu00100.inbound.protection.outlook.com`
		A	52.101.40.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy1pr05cu00402.inbound.protection.outlook.com`
		A	52.101.41.28^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01504.inbound.protection.outlook.com`
		A	52.101.42.18^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr03cu00302.inbound.protection.outlook.com`
TXT	`v=verifydomain MS=4215152`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns23.domaincontrol.com`dns@jomax.net 2019-05-15 #0

`co`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns0.centralnic.net` ⭐
	NS	`a.registrydns.co`
	NS	`b.registrydns.co`
	NS	`c.registrydns.co`
	NS	`d.registrydns.co`
	SOA	`ns0.centralnic.net`hostmaster@centralnic.net serial=1759655136

Same first word

autoconcierge.biz

autoconcierge.pl

autoconcierge.co

DNS History

14 records (4 active, 10 former)

○NSns1.bluehost.com2015-06-26 → 2017-01-31 · 4 obs

● 2015-06-26 20:00:34
● 2017-01-31 02:31:24
○ 2018-09-19 20:30:32
○ 2026-05-11 04:35:24

○NSns2.bluehost.com2015-06-26 → 2017-01-31 · 4 obs

● 2015-06-26 20:00:34
● 2017-01-31 02:31:24
○ 2018-09-19 20:30:32
○ 2026-05-11 04:35:24

●NSns23.domaincontrol.com2018-09-19 → 2026-05-11 · 3 obs

○ 2017-01-31 02:31:24
● 2018-09-19 20:30:32
● 2026-05-11 04:35:24

●NSns24.domaincontrol.com2018-09-19 → 2026-05-11 · 3 obs

○ 2017-01-31 02:31:24
● 2018-09-19 20:30:32
● 2026-05-11 04:35:24

○MXalt1.aspmx.l.google.com2015-06-26 → 2018-09-19 · 4 obs

● 2015-06-26 20:00:34
● 2018-09-19 20:30:32
○ 2026-02-16 22:04:46
○ 2026-05-11 04:35:24

○MXalt2.aspmx.l.google.com2015-06-26 → 2018-09-19 · 4 obs

● 2015-06-26 20:00:34
● 2018-09-19 20:30:32
○ 2026-02-16 22:04:46
○ 2026-05-11 04:35:24

○MXalt3.aspmx.l.google.com2015-06-26 → 2018-09-19 · 4 obs

● 2015-06-26 20:00:34
● 2018-09-19 20:30:32
○ 2026-02-16 22:04:46
○ 2026-05-11 04:35:24

○MXalt4.aspmx.l.google.com2015-06-26 → 2018-09-19 · 4 obs

● 2015-06-26 20:00:34
● 2018-09-19 20:30:32
○ 2026-02-16 22:04:46
○ 2026-05-11 04:35:24

○MXaspmx.l.google.com2015-06-26 → 2018-09-19 · 4 obs

● 2015-06-26 20:00:34
● 2018-09-19 20:30:32
○ 2026-02-16 22:04:46
○ 2026-05-11 04:35:24

●MXautoconcierge-co.mail.protection.outlook.com2026-02-16 → 2026-05-11 · 3 obs

○ 2018-09-19 20:30:32
● 2026-02-16 22:04:46
● 2026-05-11 04:35:24

○A107.20.201.1272015-11-08 → 2018-09-19 · 5 obs

○ 2015-06-26 20:00:34
● 2015-11-08 21:12:54
● 2018-09-19 20:30:32
○ 2026-02-16 22:04:46
○ 2026-05-11 04:35:24

○A52.1.244.1082018-09-19 → 2018-09-19 · 4 obs

○ 2015-11-08 21:12:54
● 2018-09-19 20:30:32
○ 2026-02-16 22:04:46
○ 2026-05-11 04:35:24

●A52.34.165.2152026-02-16 → 2026-05-11 · 3 obs

○ 2018-09-19 20:30:32
● 2026-02-16 22:04:46
● 2026-05-11 04:35:24

○A70.40.220.1022015-06-26 → 2015-06-26 · 3 obs

● 2015-06-26 20:00:34
○ 2015-11-08 21:12:54
○ 2026-05-11 04:35:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
co	c.registrydns.co, d.registrydns.co, a.registrydns.co, b.registrydns.co	-
autoconcierge.co	ns23.domaincontrol.com, ns24.domaincontrol.com	-

✅ Authoritative Response

Server:173.201.69.12

NS records: ns23.domaincontrol.com, ns24.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for autoconcierge.co (unsigned zone)

⏱️ Timing

Total: 750ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.34.165.215`
NS	2	`ns23.domaincontrol.com, ns24.domaincontrol.com`
MX	1	`autoconcierge-co.mail.protection.outlook`
TXT	2	`v=verifydomain MS=4215152, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns23.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

autoconcierge.co resolves to one IP number: 52.34.165.215.

Other host names for instance autoconcierge.biz and www.autoconcierge.net share IP numbers with autoconcierge.co.

Name Servers

autoconcierge.co's delegation uses two name servers: ns23.domaincontrol.com and ns24.domaincontrol.com.

autoconcierge.co uses the same name server setup as other domains, such as walkman.us, telecoup.com, tysa.us, amberslaughter.com and martiansrus.com.

autoconcierge.co at least partially shares name servers with other domains, for example umanasoto.com.

Host names with two IPs:

ns23.domaincontrol.com points to 2603:5:2151::c and 97.74.101.12

ns24.domaincontrol.com points to 2603:5:2251::c and 173.201.69.12

Mail Servers

A single mail server handles autoconcierge.co, autoconcierge-co.mail.protection.outlook.com.

Host autoconcierge-co.mail.protection.outlook.com points to eight IPs: 2a01:111:f403:c922::1, 2a01:111:f403:f902::, 2a01:111:f403:f902::2, 2a01:111:f403:f90d::, 52.101.10.8, 52.101.40.2, 52.101.41.28 and 52.101.42.18.

autoconcierge.co - robtex.com