dmsecurity.co.com - dns.ninja

`dmsecurity.co.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3037::6815:59d0^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:9357^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.89.208^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.147.87^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`uma.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a92^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`uma.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c092^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`uma.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2092^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`uma.ns.cloudflare.com`
		A	108.162.192.146^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`uma.ns.cloudflare.com`
		A	172.64.32.146^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`uma.ns.cloudflare.com`
		A	173.245.58.146^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`uma.ns.cloudflare.com`
NS	`walt.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b94^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`walt.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c194^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`walt.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2194^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`walt.ns.cloudflare.com`
		A	108.162.193.148^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`walt.ns.cloudflare.com`
		A	172.64.33.148^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`walt.ns.cloudflare.com`
		A	173.245.59.148^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`walt.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c07::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.89.208, 172.67.147.87
		IPv6 hints	2606:4700:3037::6815:59d0, 2606:4700:3037::ac43:9357
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=147, name=cloudflare-ech.com
SOA	`uma.ns.cloudflare.com`dns@cloudflare.com serial=2410028872

`co.com`

	DNSSEC	🔒 Signed (DS record present)
	A	169.60.151.232^{🇺🇸 SOFTLAYER169.60.128.0/18 -dal13}
	NS	`ns0.nic.co.com` ⭐
	NS	`ns1.nic.co.com`
	NS	`ns2.nic.co.com`
	NS	`ns3.nic.co.com`
	NS	`ns4.nic.co.com`
	MX	`mx.spamexperts.com` ⭐
	MX	`fallbackmx.spamexperts.eu`⁽²⁰⁾
	MX	`lastmx.spamexperts.net`⁽³⁰⁾
	TXT	`google-site-verification=7OcubotXUUSYYCSil8JjPJ_2uxorUHKIpmbUGsV_caA`
	TXT	`v=spf1 mx ip4:169.60.151.232 ip4:184.172.61.109 ip4:169.60.163.139 ip4:169.60...`
	SOA	`ns0.nic.co.com`hostmaster@co.com serial=2014419850

rank #556 globally
rank #330 in the tld

co.com

Co.com is a domain platform that offers.comdomain owners with second-level names ending in "co" the ability to promote a shorter branded web address, and it is also known as a premium/generic domain marketed for businesses seeking a short, brandable ".co"-style name while keeping the trusted.comTLD.

Key facts

Owner / operator: Neustar (historically); domain has changed hands among registry/marketing operators over time — current operator unknown with certainty
TLD:.com— gTLD
Primary purpose: branded short-domain / business identity marketing (positioned as an alternative to.coccTLD names)
Status: active

Related domains

.co— the Colombian ccTLD that is marketed globally as a generic "company/corporation" alias, conceptually related to the co.com branding proposition

📈 Tranco rank: #2,349

Same first word

dmsecurity.com

dmsecurity.nl

dmsecurity.ch

dmsecurity.com.br

dmsecurity.be

dmsecurity.co.com

dmsecurity.it

Similar names

DNS History

19 records (11 active, 8 former)

●NSuma.ns.cloudflare.com2018-05-13 → 2026-07-28 · 2 obs

● 2018-05-13 00:52:32
● 2026-07-28 04:47:50

●NSwalt.ns.cloudflare.com2018-05-13 → 2026-07-28 · 2 obs

● 2018-05-13 00:52:32
● 2026-07-28 04:47:50

●MXalt1.aspmx.l.google.com2018-05-13 → 2026-07-28 · 2 obs

● 2018-05-13 00:52:32
● 2026-07-28 04:47:50

●MXalt2.aspmx.l.google.com2018-05-13 → 2026-07-28 · 2 obs

● 2018-05-13 00:52:32
● 2026-07-28 04:47:50

○MXalt3.aspmx.l.google.com2018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 00:52:32
○ 2026-02-28 06:31:40
○ 2026-07-28 04:47:50

○MXalt4.aspmx.l.google.com2018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 00:52:32
○ 2026-02-28 06:31:40
○ 2026-07-28 04:47:50

●MXaspmx.l.google.com2018-05-13 → 2026-07-28 · 2 obs

● 2018-05-13 00:52:32
● 2026-07-28 04:47:50

●MXaspmx2.googlemail.com2026-02-28 → 2026-07-28 · 3 obs

○ 2018-05-13 00:52:32
● 2026-02-28 06:31:40
● 2026-07-28 04:47:50

●MXaspmx3.googlemail.com2026-02-28 → 2026-07-28 · 3 obs

○ 2018-05-13 00:52:32
● 2026-02-28 06:31:40
● 2026-07-28 04:47:50

●A104.21.89.2082026-02-28 → 2026-07-28 · 3 obs

○ 2018-05-13 00:52:32
● 2026-02-28 06:31:40
● 2026-07-28 04:47:50

○A104.25.167.1072018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 00:52:32
○ 2026-02-28 06:31:40
○ 2026-07-28 04:47:50

○A104.25.168.1072018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 00:52:32
○ 2026-02-28 06:31:40
○ 2026-07-28 04:47:50

●A172.67.147.872026-02-28 → 2026-07-28 · 3 obs

○ 2018-05-13 00:52:32
● 2026-02-28 06:31:40
● 2026-07-28 04:47:50

○A2400:cb00:2048:1::6819:a76b2018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 00:52:32
○ 2026-02-28 06:31:40
○ 2026-07-28 04:47:50

○A2400:cb00:2048:1::6819:a86b2018-05-13 → 2018-05-13 · 3 obs

● 2018-05-13 00:52:32
○ 2026-02-28 06:31:40
○ 2026-07-28 04:47:50

○A2606:4700:3033::6815:59d02026-02-28 → 2026-02-28 · 4 obs

○ 2018-05-13 00:52:32
● 2026-02-28 06:31:40
○ 2026-07-13 02:02:10
○ 2026-07-28 04:47:50

○A2606:4700:3034::ac43:93572026-02-28 → 2026-02-28 · 4 obs

○ 2018-05-13 00:52:32
● 2026-02-28 06:31:40
○ 2026-07-13 02:02:10
○ 2026-07-28 04:47:50

●A2606:4700:3037::6815:59d02026-07-13 → 2026-07-28 · 3 obs

○ 2026-02-28 06:31:40
● 2026-07-13 02:02:10
● 2026-07-28 04:47:50

●A2606:4700:3037::ac43:93572026-07-13 → 2026-07-28 · 3 obs

○ 2026-02-28 06:31:40
● 2026-07-13 02:02:10
● 2026-07-28 04:47:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net...	-
co.com	ns1.nic.co.com, ns2.nic.co.com, ns3.nic.co.com, ns4.nic.co.com	8 records
dmsecurity.co.com	uma.ns.cloudflare.com, walt.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.193.148

NS records: uma.ns.cloudflare.com, walt.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dmsecurity.co.com (unsigned zone)

⏱️ Timing

Total: 1391ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.89.208, 172.67.147.87`
AAAA	2	`2606:4700:3037::ac43:9357, 2606:4700:3037::6815:59d0`
NS	2	`uma.ns.cloudflare.com, walt.ns.cloudflare.com`
MX	5	`aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`uma.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 8

In-bailiwick: 8 (ns1.nic.co.com, ns1.nic.co.com, ns2.nic.co.com...)

Analysis

IP Addresses

dmsecurity.co.com directs to four IP numbers, which are 104.21.89.208, 172.67.147.87, 2606:4700:3037::6815:59d0 and 2606:4700:3037::ac43:9357.

f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.f7272f1878c2.gorowandpaddle.org, www.aficom.net, ffr.mobi and two other host names share IP numbers with dmsecurity.co.com.

Name Servers

Two name servers handle the delegation for dmsecurity.co.com: uma.ns.cloudflare.com and walt.ns.cloudflare.com.

dmsecurity.co.com uses the same name servers as several other domains — among them minidokids.com, mcec.io, host88.net and two more.

There is at least partial name server overlap between dmsecurity.co.com and other domains — ypscraper.com, clinkclink.co.uk, meta-gatecorex.pages.dev and two more among them.

These name servers are routinely deployed together with the name servers kim.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

uma.ns.cloudflare.com resolves to 108.162.192.146, 172.64.32.146 and 173.245.58.146 among others, with 3 other IP addresses in total.

walt.ns.cloudflare.com resolves to 108.162.193.148, 172.64.33.148 and 173.245.59.148 among others, with 3 other IP addresses in total.

Mail Servers

Five mail servers handle dmsecurity.co.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

dmsecurity.co.com has at least partial mail server overlap with other domains such as ns500731.ns500754.ns500742.ns500754.ns500671.ns500742.ns500742.ns500705.ns500671.ns500678.ns500671.ns500705.ns500678.ns500666.ns500666.ns500153.tenderladiesbz.com, ns500734.ns500734.ns500693.ns500699.ns500699.ns500693.ns500693.ns500693.ns500693.ns500699.ns500693.ns500612.ns500632.ns500612.dtrkdll.com, ns500742.ns500731.ns500754.ns500754.ns500754.ns500742.ns500731.ns500678.ns500678.ns500291.ns500671.ns500666.ns500153.tenderladiesbz.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 3 others.

Hostnames that resolve to two IP addresses:

aspmx2.googlemail.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.

aspmx3.googlemail.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com resolves to two addresses: 64.233.180.27 and 2607:f8b0:4004:c07::1a.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.

aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 2a00:1450:400b:c02::1a IP addresses.