`linkingplatform.com`

DNSSEC	⚠️ Not signed
A	65.181.113.31^{🇬🇧 WHG-FRA65.181.113.0/24}
NS	`ns1.mysecurecloudhost.com` ⭐ ⚠️ Not in parent delegation
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns1.verpex.com` ⚠️ Not in zone NS records
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns2.mysecurecloudhost.com` ⚠️ Not in parent delegation
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns2.verpex.com` ⚠️ Not in zone NS records
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns3.mysecurecloudhost.com` ⚠️ Not in parent delegation
		A	76.223.26.245^{🇺🇸 Amazon76.223.16.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns3.verpex.com` ⚠️ Not in zone NS records
		A	76.223.26.245^{🇺🇸 Amazon76.223.16.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns4.mysecurecloudhost.com` ⚠️ Not in parent delegation
		A	99.83.147.209^{🇺🇸 Amazon99.83.144.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns4.verpex.com` ⚠️ Not in zone NS records
		A	99.83.147.209^{🇺🇸 Amazon99.83.144.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
MX	`linkingplatform.com` ⭐
		A	65.181.113.31^{🇬🇧 WHG-FRA65.181.113.0/24}
TXT	`v=spf1 +a +mx +ip4:65.181.113.31 include:spf.mysecurecloudhost.com ~all`
SOA	`ns1.mysecurecloudhost.com`servers@mysecurecloudhost.com 2026-07-03 #0

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

MX for

linkingplatform.com

Same first word

linkingplatform.com

DNS History

15 records (10 active, 5 former)

●NSns1.mysecurecloudhost.com2026-02-27 → 2026-07-23 · 3 obs

○ 2017-05-09 06:57:44
● 2026-02-27 15:10:36
● 2026-07-23 08:04:24

●NSns1.verpex.com2026-02-27 → 2026-07-23 · 3 obs

○ 2017-05-09 06:57:44
● 2026-02-27 15:10:36
● 2026-07-23 08:04:24

○NSns1jlp.name.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 06:57:44
○ 2026-02-27 15:10:36
○ 2026-07-23 08:04:24

●NSns2.mysecurecloudhost.com2026-02-27 → 2026-07-23 · 3 obs

○ 2017-05-09 06:57:44
● 2026-02-27 15:10:36
● 2026-07-23 08:04:24

●NSns2.verpex.com2026-02-27 → 2026-07-23 · 3 obs

○ 2017-05-09 06:57:44
● 2026-02-27 15:10:36
● 2026-07-23 08:04:24

○NSns2jrt.name.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 06:57:44
○ 2026-02-27 15:10:36
○ 2026-07-23 08:04:24

●NSns3.mysecurecloudhost.com2026-02-27 → 2026-07-23 · 3 obs

○ 2017-05-09 06:57:44
● 2026-02-27 15:10:36
● 2026-07-23 08:04:24

●NSns3.verpex.com2026-02-27 → 2026-07-23 · 3 obs

○ 2017-05-09 06:57:44
● 2026-02-27 15:10:36
● 2026-07-23 08:04:24

○NSns3bfm.name.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 06:57:44
○ 2026-02-27 15:10:36
○ 2026-07-23 08:04:24

●NSns4.mysecurecloudhost.com2026-02-27 → 2026-07-23 · 3 obs

○ 2017-05-09 06:57:44
● 2026-02-27 15:10:36
● 2026-07-23 08:04:24

●NSns4.verpex.com2026-02-27 → 2026-07-23 · 3 obs

○ 2017-05-09 06:57:44
● 2026-02-27 15:10:36
● 2026-07-23 08:04:24

○NSns4bty.name.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 06:57:44
○ 2026-02-27 15:10:36
○ 2026-07-23 08:04:24

●MXlinkingplatform.com2026-02-27 → 2026-07-23 · 2 obs

● 2026-02-27 15:10:36
● 2026-07-23 08:04:24

●A65.181.113.312026-02-27 → 2026-07-23 · 3 obs

○ 2017-05-09 06:57:44
● 2026-02-27 15:10:36
● 2026-07-23 08:04:24

○A95.211.81.1932017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 06:57:44
○ 2026-02-27 15:10:36
○ 2026-07-23 08:04:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, j.gtld-servers.net, c.gtld-servers.net, h.gtld-servers.net...	-
linkingplatform.com	ns1.verpex.com, ns2.verpex.com, ns3.verpex.com, ns4.verpex.com	4 records

✅ Authoritative Response

Server:76.223.26.245

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for linkingplatform.com (unsigned zone)

⏱️ Timing

Total: 979ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`65.181.113.31`
NS	4	`ns3.mysecurecloudhost.com, ns1.mysecurecloudhost.com...`
MX	1	`linkingplatform.com (pri: 0)`
TXT	1	`v=spf1 +a +mx +ip4:65.181.113.31 include`
SOA	1	`ns1.mysecurecloudhost.com servers.mysecu`

📌 Glue Records Collected

Total: 4

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

Analysis

Mail Server Role

linkingplatform.com serves as a mail server for linkingplatform.com.

IP Addresses

linkingplatform.com has exactly one IP address — 65.181.113.31.

europartners.al, consap.eu, el-ca.com plus two other host names have IP numbers in common with linkingplatform.com.

Name Servers

linkingplatform.com delegates authority to 8 name servers: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com plus 5 other.

linkingplatform.com has at least partial name server overlap with other domains, such as cambodiawebmaster.com, serenitycreams.com, fc.co.mz and two others.

ns4.mysecurecloudhost.com, ns2.verpex.com and ns1.verpex.com — plus 4 other name servers — are commonly paired with these name servers.

Host names resolving to a single IP address:

ns1.mysecurecloudhost.com has the IP address 13.248.158.180.

ns2.mysecurecloudhost.com has the IP address 75.2.118.134.

ns3.mysecurecloudhost.com has the IP address 76.223.26.245.

ns4.mysecurecloudhost.com has the IP address 99.83.147.209.

ns1.verpex.com has the IP address 13.248.158.180.

ns2.verpex.com has the IP address 75.2.118.134.

ns3.verpex.com has the IP address 76.223.26.245.

ns4.verpex.com has the IP address 99.83.147.209.

Both ns1.mysecurecloudhost.com and ns1.verpex.com resolve to 13.248.158.180 IP addresses each.

Both ns2.mysecurecloudhost.com and ns2.verpex.com resolve to 75.2.118.134 IP addresses each.