corecomponents.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`corecomponents.com`

DNSSEC	⚠️ Not signed
A	169.61.52.206^{🇺🇸 SOFTLAYER169.61.0.0/18 -dal13}
		PTR	`ce.34.3da9.ip4.static.sl-reverse.com`
NS	`ns1.chinetworks.com` ⭐
		A	204.80.92.40^{🇺🇸 AS18590204.80.92.0/24 US Signal downstream customer}
NS	`ns2.chinetworks.com`
		A	170.178.144.85^{🇺🇸 AS18590170.178.144.0/24}
NS	`ns3.chinetworks.com` ⚠️ Not in zone NS records
		A	170.178.147.31^{🇺🇸 AS18590170.178.147.0/24}
NS	`ns4.chinetworks.com` ⚠️ Not in zone NS records
NS	`ns5.chinetworks.com` ⚠️ Not in zone NS records
MX	`corecomponents-com.inbound.emailservice.io` ⭐
		A	3.223.82.138^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-223-82-138.compute-1.amazonaws.com`
		A	18.204.58.103^{🇺🇸 Amazon18.204.0.0/14 EC2 IAD prefix}
			PTR	`ec2-18-204-58-103.compute-1.amazonaws.com`
		A	44.216.32.179^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-216-32-179.compute-1.amazonaws.com`
MX	`corecomponents-com.inbound.emailservice.co`⁽²⁰⁾
		A	3.223.82.138^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-223-82-138.compute-1.amazonaws.com`
		A	18.204.58.103^{🇺🇸 Amazon18.204.0.0/14 EC2 IAD prefix}
			PTR	`ec2-18-204-58-103.compute-1.amazonaws.com`
		A	44.216.32.179^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-216-32-179.compute-1.amazonaws.com`
MX	`corecomponents-com.inbound.emailservice.cc`⁽³⁰⁾
		A	3.223.82.138^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-223-82-138.compute-1.amazonaws.com`
		A	18.204.58.103^{🇺🇸 Amazon18.204.0.0/14 EC2 IAD prefix}
			PTR	`ec2-18-204-58-103.compute-1.amazonaws.com`
		A	44.216.32.179^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ec2-44-216-32-179.compute-1.amazonaws.com`
TXT	`v=spf1 include:_spfa.chinetworks.com include:_spfb.chinetworks.com -all`
SOA	`ns1.chinetworks.com`support@chinetworks.com 2026-03-16 #6

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

Same first word

corecomponents.com

corecomponents.ie

Similar names

cerocomponents.co.uk

DNS History

12 records (9 active, 3 former)

●NSns1.chinetworks.com2015-05-15 → 2026-08-17 · 2 obs

● 2015-05-15 01:44:42
● 2026-08-17 12:25:00

●NSns2.chinetworks.com2015-05-15 → 2026-08-17 · 2 obs

● 2015-05-15 01:44:42
● 2026-08-17 12:25:00

●NSns3.chinetworks.com2026-05-14 → 2026-08-17 · 3 obs

○ 2015-05-15 01:44:42
● 2026-05-14 09:32:04
● 2026-08-17 12:25:00

●NSns4.chinetworks.com2026-05-14 → 2026-08-17 · 3 obs

○ 2015-05-15 01:44:42
● 2026-05-14 09:32:04
● 2026-08-17 12:25:00

●NSns5.chinetworks.com2026-05-18 → 2026-08-17 · 3 obs

○ 2026-05-14 09:32:04
● 2026-05-18 21:41:26
● 2026-08-17 12:25:00

●MXcorecomponents-com.inbound.emailservice.cc2026-03-03 → 2026-08-17 · 3 obs

○ 2016-09-02 15:23:32
● 2026-03-03 13:55:58
● 2026-08-17 12:25:00

●MXcorecomponents-com.inbound.emailservice.co2026-03-03 → 2026-08-17 · 3 obs

○ 2016-09-02 15:23:32
● 2026-03-03 13:55:58
● 2026-08-17 12:25:00

●MXcorecomponents-com.inbound.emailservice.io2026-03-03 → 2026-08-17 · 3 obs

○ 2016-09-02 15:23:32
● 2026-03-03 13:55:58
● 2026-08-17 12:25:00

○MXsmtp01.wncloud.com2015-05-15 → 2016-09-02 · 4 obs

● 2015-05-15 01:44:42
● 2016-09-02 15:23:32
○ 2026-03-03 13:55:58
○ 2026-08-17 12:25:00

○MXsmtp02.wncloud.com2015-05-15 → 2016-09-02 · 4 obs

● 2015-05-15 01:44:42
● 2016-09-02 15:23:32
○ 2026-03-03 13:55:58
○ 2026-08-17 12:25:00

●A169.61.52.2062026-03-03 → 2026-08-17 · 3 obs

○ 2016-09-02 15:23:32
● 2026-03-03 13:55:58
● 2026-08-17 12:25:00

○A204.80.91.612015-05-15 → 2016-09-02 · 4 obs

● 2015-05-15 01:44:42
● 2016-09-02 15:23:32
○ 2026-03-03 13:55:58
○ 2026-08-17 12:25:00

🔍 DNS Trace

Analysis

IP Addresses

corecomponents.com has exactly one IP address — 169.61.52.206.

co.cherokee.tx.us, ferrisarch.com, smtp.apache-it.com plus two other host names have IP numbers in common with corecomponents.com.

Name Servers

Five name servers handle delegation for corecomponents.com: ns1.chinetworks.com, ns2.chinetworks.com, ns3.chinetworks.com and two others.

At least some of corecomponents.com's name servers are shared with other domains, for example chinetworks.de, 189.213.162.in-addr.arpa, 200.245.103.in-addr.arpa and two more.

These name servers tend to be deployed in combination with the name servers ns4.chinetworks.com and ns5.chinetworks.com.

Three hostnames, one IP address apiece: ns1.chinetworks.com resolves to 204.80.92.40, ns2.chinetworks.com resolves to 170.178.144.85 and ns3.chinetworks.com resolves to 170.178.147.31.

Mail Servers

The MX records for corecomponents.com list three mail servers: corecomponents-com.inbound.emailservice.cc, corecomponents-com.inbound.emailservice.co and corecomponents-com.inbound.emailservice.io.

corecomponents-com.inbound.emailservice.cc resolves to 3.223.82.138, 18.204.58.103 and 44.216.32.179; corecomponents-com.inbound.emailservice.co resolves to 3.223.82.138, 18.204.58.103 and 44.216.32.179; and corecomponents-com.inbound.emailservice.io resolves to 3.223.82.138, 18.204.58.103 and 44.216.32.179 — all three hosts map to the same IP addresses.

Three host names point to 3.223.82.138: corecomponents-com.inbound.emailservice.cc, corecomponents-com.inbound.emailservice.co and corecomponents-com.inbound.emailservice.io.

Three host names point to 18.204.58.103: corecomponents-com.inbound.emailservice.cc, corecomponents-com.inbound.emailservice.co and corecomponents-com.inbound.emailservice.io.

Three host names point to 44.216.32.179: corecomponents-com.inbound.emailservice.cc, corecomponents-com.inbound.emailservice.co and corecomponents-com.inbound.emailservice.io.