securemcp.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`securemcp.com`

DNSSEC	⚠️ Not signed
A	3.33.130.190^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`a2aa9ff50de748dbe.awsglobalaccelerator.com`
A	15.197.148.33^{🇺🇸 Amazon15.197.144.0/20}
NS	`ns21.domaincontrol.com` ⭐
		A	2603:5:2141::b^{🇺🇸 GODADDY-DNS2603:5:2140::/44}
			PTR	`ns21.domaincontrol.com`
		A	97.74.100.11^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns21.domaincontrol.com`
NS	`ns22.domaincontrol.com`
		A	2603:5:2241::b^{🇺🇸 GODADDY-DNS2603:5:2240::/44}
			PTR	`ns22.domaincontrol.com`
		A	173.201.68.11^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns22.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	192.178.218.26^{🇺🇸 Google192.178.218.0/24}
			PTR	`yuiadtq-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=s-N_qehHIVFsHwAUcuYQQl2DWOvA7Fi7sfWwCbxYyGg`
TXT	`v=spf1 include:dc-aa8e722993._spfm.securemcp.com ~all`
SOA	`ns21.domaincontrol.com`dns@jomax.net 2025-02-15 #7

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

Previously MX for

securemcp.com

Same first word

securemcp.com

Similar names

supremecc.cloudapp.net

securempc.com

ccsupreme.com

pcmsecure.com

DNS History

25 records (9 active, 16 former)

○NSns1.christiancdn.com2015-08-10 → 2015-11-29 · 4 obs

● 2015-08-10 07:48:42
● 2015-11-29 14:01:34
○ 2016-03-01 23:15:16
○ 2026-08-15 22:22:48

○NSns1.teleredcristiana.net2016-03-01 → 2016-07-04 · 5 obs

○ 2015-11-29 14:01:34
● 2016-03-01 23:15:16
● 2016-07-04 07:25:56
○ 2017-05-24 02:39:24
○ 2026-08-15 22:22:48

○NSns2.christiancdn.com2015-08-10 → 2015-11-29 · 4 obs

● 2015-08-10 07:48:42
● 2015-11-29 14:01:34
○ 2016-03-01 23:15:16
○ 2026-08-15 22:22:48

○NSns2.teleredcristiana.net2016-03-01 → 2016-07-04 · 5 obs

○ 2015-11-29 14:01:34
● 2016-03-01 23:15:16
● 2016-07-04 07:25:56
○ 2017-05-24 02:39:24
○ 2026-08-15 22:22:48

●NSns21.domaincontrol.com2026-03-01 → 2026-08-15 · 3 obs

○ 2017-05-24 02:39:24
● 2026-03-01 23:50:04
● 2026-08-15 22:22:48

●NSns22.domaincontrol.com2026-03-01 → 2026-08-15 · 3 obs

○ 2017-05-24 02:39:24
● 2026-03-01 23:50:04
● 2026-08-15 22:22:48

○NSns3.christiancdn.com2015-08-10 → 2015-11-29 · 4 obs

● 2015-08-10 07:48:42
● 2015-11-29 14:01:34
○ 2016-03-01 23:15:16
○ 2026-08-15 22:22:48

○NSns3.teleredcristiana.net2016-03-01 → 2016-07-04 · 5 obs

○ 2015-11-29 14:01:34
● 2016-03-01 23:15:16
● 2016-07-04 07:25:56
○ 2017-05-24 02:39:24
○ 2026-08-15 22:22:48

○NSns4.christiancdn.com2015-08-10 → 2015-11-29 · 4 obs

● 2015-08-10 07:48:42
● 2015-11-29 14:01:34
○ 2016-03-01 23:15:16
○ 2026-08-15 22:22:48

○NSns4.teleredcristiana.net2016-03-01 → 2016-07-04 · 5 obs

○ 2015-11-29 14:01:34
● 2016-03-01 23:15:16
● 2016-07-04 07:25:56
○ 2017-05-24 02:39:24
○ 2026-08-15 22:22:48

○NSns41.domaincontrol.com2017-05-24 → 2017-05-24 · 4 obs

○ 2016-07-04 07:25:56
● 2017-05-24 02:39:24
○ 2026-03-01 23:50:04
○ 2026-08-15 22:22:48

○NSns42.domaincontrol.com2017-05-24 → 2017-05-24 · 4 obs

○ 2016-07-04 07:25:56
● 2017-05-24 02:39:24
○ 2026-03-01 23:50:04
○ 2026-08-15 22:22:48

●MXalt1.aspmx.l.google.com2026-03-01 → 2026-08-15 · 3 obs

○ 2017-05-24 02:39:24
● 2026-03-01 23:50:04
● 2026-08-15 22:22:48

●MXalt2.aspmx.l.google.com2026-03-01 → 2026-08-15 · 3 obs

○ 2017-05-24 02:39:24
● 2026-03-01 23:50:04
● 2026-08-15 22:22:48

●MXalt3.aspmx.l.google.com2026-03-01 → 2026-08-15 · 3 obs

○ 2017-05-24 02:39:24
● 2026-03-01 23:50:04
● 2026-08-15 22:22:48

●MXalt4.aspmx.l.google.com2026-03-01 → 2026-08-15 · 3 obs

○ 2017-05-24 02:39:24
● 2026-03-01 23:50:04
● 2026-08-15 22:22:48

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

○ 2017-05-24 02:39:24
● 2026-03-01 23:50:04
● 2026-08-15 22:22:48

○MXmailstore1.secureserver.net2017-05-24 → 2017-05-24 · 4 obs

○ 2016-07-04 07:25:56
● 2017-05-24 02:39:24
○ 2026-03-01 23:50:04
○ 2026-08-15 22:22:48

○MXsecuremcp.com2015-08-10 → 2016-07-04 · 4 obs

● 2015-08-10 07:48:42
● 2016-07-04 07:25:56
○ 2017-05-24 02:39:24
○ 2026-08-15 22:22:48

○MXsmtp.secureserver.net2017-05-24 → 2017-05-24 · 4 obs

○ 2016-07-04 07:25:56
● 2017-05-24 02:39:24
○ 2026-03-01 23:50:04
○ 2026-08-15 22:22:48

○A142.4.218.2182017-05-24 → 2017-05-24 · 4 obs

○ 2016-07-04 07:25:56
● 2017-05-24 02:39:24
○ 2026-03-01 23:50:04
○ 2026-08-15 22:22:48

●A15.197.148.332026-03-01 → 2026-08-15 · 3 obs

○ 2017-05-24 02:39:24
● 2026-03-01 23:50:04
● 2026-08-15 22:22:48

○A158.69.225.1662016-03-01 → 2016-07-04 · 5 obs

○ 2015-11-29 14:01:34
● 2016-03-01 23:15:16
● 2016-07-04 07:25:56
○ 2017-05-24 02:39:24
○ 2026-08-15 22:22:48

○A206.225.80.302015-08-10 → 2015-11-29 · 4 obs

● 2015-08-10 07:48:42
● 2015-11-29 14:01:34
○ 2016-03-01 23:15:16
○ 2026-08-15 22:22:48

●A3.33.130.1902026-03-01 → 2026-08-15 · 3 obs

○ 2017-05-24 02:39:24
● 2026-03-01 23:50:04
● 2026-08-15 22:22:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, f.gtld-servers.net, d.gtld-servers.net, h.gtld-servers.net...	-
securemcp.com	ns21.domaincontrol.com, ns22.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.100.11

NS records: ns21.domaincontrol.com, ns22.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securemcp.com (unsigned zone)

⏱️ Timing

Total: 209ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.33.130.190, 15.197.148.33`
NS	2	`ns21.domaincontrol.com, ns22.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	2	`google-site-verification=s-N_qehHIVFsHwA, v=spf1 include:dc-aa8e722993._spfm.secur`
SOA	1	`ns21.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns21.domaincontrol.com, ns21.domaincontrol.com, ns22.domaincontrol.com...)

Analysis

IP Addresses

securemcp.com has two IP addresses: 3.33.130.190 and 15.197.148.33

menstotebags.com, xyberlogic.com, ggdsinc.com plus two other host names have IP numbers in common with securemcp.com.

Name Servers

securemcp.com has two authoritative name servers — ns21.domaincontrol.com and ns22.domaincontrol.com.

The name server configuration of securemcp.com is shared with other domains, for instance lindmor.org, holyspiritunoh.org, stormyenterprises.com and two others.

The name servers for securemcp.com overlap at least partially with those of other domains — for example staroil.info.

Both ns21.domaincontrol.com and ns22.domaincontrol.com have two IP addresses each. ns21.domaincontrol.com resolves to 97.74.100.11 and 2603:5:2141::b; ns22.domaincontrol.com resolves to 173.201.68.11 and 2603:5:2241::b.

Mail Servers

Five mail servers handle securemcp.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by securemcp.com are shared with other domains: erwinout.com, naturalstonecarpets.ie, madco.co and two others among them.

It is common to find these mail servers paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and aspmx2.googlemail.com, as well as two others.

Host names pointing to two IP addresses:

aspmx.l.google.com resolves to 192.178.218.26 and 2607:f8b0:4004:c23::1a.

alt1.aspmx.l.google.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1a.

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

alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1a.