comuserve.com - dns.ninja

`comuserve.com`

DNSSEC	⚠️ Not signed
A	169.197.85.37^{🇺🇸 PureVoltage169.197.80.0/21}
A	169.197.85.38^{🇺🇸 PureVoltage169.197.80.0/21}
NS	`ns1.comuserve.com` ⭐
		A	66.117.19.194^{🇺🇸 Amazon66.117.19.0/24 EC2 Prefix}
			PTR	`r194.reserve.bestwestern.com`
		A	169.197.85.52^{🇺🇸 PureVoltage169.197.80.0/21}
NS	70.42.254.112 ⚠️ Not in parent delegation
NS	`ns1.synacortechnologies.com`
		A	169.197.85.52^{🇺🇸 PureVoltage169.197.80.0/21}
NS	`ns2.synacortechnologies.com`
		A	169.197.85.53^{🇺🇸 PureVoltage169.197.80.0/21}
NS	`ns3.synacortechnologies.com`
		A	72.219.237.159^{🇺🇸 AS1217472.219.237.0/24 V4-PUB-CB-AGGREGATE}
			PTR	`wsip-72-219-237-159.lv.lv.cox.net`
NS	`ns4.synacortechnologies.com`
		A	72.219.237.160^{🇺🇸 AS1217472.219.237.0/24 V4-PUB-CB-AGGREGATE}
			PTR	`wsip-72-219-237-160.lv.lv.cox.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c07::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f26.1e100.net`
		A	172.253.115.26^{🇺🇸 Google172.253.115.0/24}
			PTR	`bg-in-f26.1e100.net`
TXT	`v=spf1 ip4:70.42.254.0/24 ip4:64.74.172.0/24 ~all`
SOA	`ns1.comuserve.com`hostmaster@comuserve.com serial=3

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

Subdomains

ns1.comuserve.com

Same first word

comuserve.com

Similar names

ecoversum.at

sevumcore.click

uscoverme.com

sumocerve.com.pt

securmove.com

DNS History

21 records (9 active, 12 former)

●NS70.42.254.1122015-07-26 → 2026-08-03 · 5 obs

● 2015-07-26 13:44:26
○ 2015-09-17 09:40:40
○ 2017-09-19 07:25:26
● 2026-03-18 20:23:30
● 2026-08-03 04:55:34

○NS70.42.254.1122015-09-17 → 2017-06-22 · 7 obs

○ 2015-07-26 13:44:26
● 2015-09-17 09:40:40
● 2016-01-05 01:12:04
○ 2016-01-16 23:47:38
● 2017-06-22 01:49:16
○ 2017-07-08 16:56:20
○ 2026-08-03 04:55:34

○NSns1.colo.com2016-01-16 → 2017-06-22 · 5 obs

○ 2016-01-05 01:12:04
● 2016-01-16 23:47:38
● 2017-06-22 01:49:16
○ 2017-07-08 16:56:20
○ 2026-08-03 04:55:34

●NSns1.comuserve.com2026-03-18 → 2026-08-03 · 3 obs

○ 2017-09-19 07:25:26
● 2026-03-18 20:23:30
● 2026-08-03 04:55:34

○NSns1.ndsplitter.com2017-07-08 → 2017-09-19 · 5 obs

○ 2017-06-22 01:49:16
● 2017-07-08 16:56:20
● 2017-09-19 07:25:26
○ 2026-03-18 20:23:30
○ 2026-08-03 04:55:34

●NSns1.synacortechnologies.com2026-03-18 → 2026-08-03 · 3 obs

○ 2017-09-19 07:25:26
● 2026-03-18 20:23:30
● 2026-08-03 04:55:34

○NSns2.ndsplitter.com2017-07-08 → 2017-09-19 · 5 obs

○ 2017-06-22 01:49:16
● 2017-07-08 16:56:20
● 2017-09-19 07:25:26
○ 2026-03-18 20:23:30
○ 2026-08-03 04:55:34

●NSns2.synacortechnologies.com2026-03-18 → 2026-08-03 · 3 obs

○ 2017-09-19 07:25:26
● 2026-03-18 20:23:30
● 2026-08-03 04:55:34

○NSns3.ndsplitter.com2017-07-08 → 2017-09-19 · 5 obs

○ 2017-06-22 01:49:16
● 2017-07-08 16:56:20
● 2017-09-19 07:25:26
○ 2026-03-18 20:23:30
○ 2026-08-03 04:55:34

●NSns3.synacortechnologies.com2026-03-18 → 2026-08-03 · 3 obs

○ 2017-09-19 07:25:26
● 2026-03-18 20:23:30
● 2026-08-03 04:55:34

●NSns4.synacortechnologies.com2026-03-18 → 2026-08-03 · 3 obs

○ 2017-09-19 07:25:26
● 2026-03-18 20:23:30
● 2026-08-03 04:55:34

●MXaspmx.l.google.com2026-03-18 → 2026-08-03 · 3 obs

○ 2017-07-08 16:56:20
● 2026-03-18 20:23:30
● 2026-08-03 04:55:34

○MXmail.comuserve.com2015-07-26 → 2017-06-22 · 4 obs

● 2015-07-26 13:44:26
● 2017-06-22 01:49:16
○ 2017-07-08 16:56:20
○ 2026-08-03 04:55:34

○A144.76.0.2422017-07-08 → 2017-09-19 · 5 obs

○ 2017-06-22 01:49:16
● 2017-07-08 16:56:20
● 2017-09-19 07:25:26
○ 2026-03-18 20:23:30
○ 2026-08-03 04:55:34

○A144.76.1.1302017-07-08 → 2017-09-19 · 5 obs

○ 2017-06-22 01:49:16
● 2017-07-08 16:56:20
● 2017-09-19 07:25:26
○ 2026-03-18 20:23:30
○ 2026-08-03 04:55:34

●A169.197.85.372026-03-18 → 2026-08-03 · 7 obs

○ 2017-09-19 07:25:26
● 2026-03-18 20:23:30
● 2026-04-06 15:43:38
○ 2026-04-08 18:04:32
○ 2026-04-10 13:11:16
● 2026-05-28 21:07:04
● 2026-08-03 04:55:34

●A169.197.85.382026-03-18 → 2026-08-03 · 7 obs

○ 2017-09-19 07:25:26
● 2026-03-18 20:23:30
● 2026-04-06 15:43:38
○ 2026-04-08 18:04:32
○ 2026-04-10 13:11:16
● 2026-05-28 21:07:04
● 2026-08-03 04:55:34

○A64.74.172.1252015-07-26 → 2016-01-21 · 4 obs

● 2015-07-26 13:44:26
● 2016-01-21 07:15:18
○ 2016-01-29 07:27:56
○ 2026-08-03 04:55:34

○A66.63.171.1252016-01-29 → 2017-06-22 · 5 obs

○ 2016-01-21 07:15:18
● 2016-01-29 07:27:56
● 2017-06-22 01:49:16
○ 2017-07-08 16:56:20
○ 2026-08-03 04:55:34

○A72.219.237.182026-04-08 → 2026-04-10 · 5 obs

○ 2026-04-06 15:43:38
● 2026-04-08 18:04:32
● 2026-04-10 13:11:16
○ 2026-05-28 21:07:04
○ 2026-08-03 04:55:34

○A72.219.237.192026-04-08 → 2026-04-10 · 5 obs

○ 2026-04-06 15:43:38
● 2026-04-08 18:04:32
● 2026-04-10 13:11:16
○ 2026-05-28 21:07:04
○ 2026-08-03 04:55:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, i.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net...	-
comuserve.com	ns1.synacortechnologies.com, ns2.synacortechnologies.com, ns3.synacortechnologies.com, ns4.synacortechnologies.com	4 records

✅ Authoritative Response

Server:169.197.85.52

NS records: ns1.synacortechnologies.com, ns2.synacortechnologies.com, ns3.synacortechnologies.com, ns4.synacortechnologies.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for comuserve.com (unsigned zone)

⏱️ Timing

Total: 329ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`169.197.85.37, 169.197.85.38`
NS	5	`ns1.synacortechnologies.com, ns2.synacortechnologies.com...`
MX	1	`aspmx.l.google.com (pri: 10)`
TXT	1	`v=spf1 ip4:70.42.254.0/24 ip4:64.74.172.`
SOA	1	`ns1.comuserve.com hostmaster.comuserve.c`

📌 Glue Records Collected

Total: 4

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

Analysis

Hierarchy

comuserve.com is a parent domain of ns1.comuserve.com.

IP Addresses

comuserve.com directs to two IP numbers, 169.197.85.37 and 169.197.85.38

positiontechnique.com, airportsearches.com, onechasebank.com and two other host names share IP numbers with comuserve.com.

Name Servers

DNS for comuserve.com is handled by 6 name servers: ns1.comuserve.com, ns1.synacortechnologies.com, ns2.synacortechnologies.com and 3 others.

comuserve.com shares at least some of its name servers with other domains, including airbrushing411.com, airportarkansas.com, sprins.com and two others.

These name servers are frequently seen alongside ns3.synacortechnologies.com, ns4.synacortechnologies.com, 70.42.254.112 and 7 other name servers.

Hostnames that resolve to two IP addresses:

ns1.comuserve.com has two IP addresses: 66.117.19.194 and 169.197.85.52.

Hosts with just one IP address:

ns1.synacortechnologies.com directs to 169.197.85.52.

ns2.synacortechnologies.com directs to 169.197.85.53.

ns3.synacortechnologies.com directs to 72.219.237.159.

ns4.synacortechnologies.com directs to 72.219.237.160.

Host names pointing to 169.197.85.52 IP addresses: ns1.comuserve.com and ns1.synacortechnologies.com.

Mail Servers

Mail for comuserve.com is handled by a single mail server, aspmx.l.google.com.

comuserve.com uses an identical mail server configuration to several other domains — among them smartmom.wpengine.com, tykomedia.asia, dpacinc.com and two more.

comuserve.com has at least partial mail server overlap with other domains such as 137.ca, ns500599.ns500724.ns500599.ns500737.ns500724.ns500724.ns500724.ns500724.ns500724.ns500583.ns500697.ns500583.ns500599.ns500669.www.yummyflingsfinder.com, ns500754.ns500742.ns500742.ns500754.ns500671.ns500704.ns500731.ns500704.ns500704.ns500704.ns500666.lustychickser.com and two more.

These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 5 others.

aspmx.l.google.com points to two IP addresses: 172.253.115.26 and 2607:f8b0:4004:c07::1a.