testingforclient.com - robtex.com

🛡️Domain Reputation CheckBlocklist, phishing & malware status

testingforclient.com

DNSSEC⚠️ Not signed
A23.94.221.209🇺🇸 COLOCROSSING23.94.221.0/24 ColoCrossing
PTRkeycancelcom.guiran.me
NSns1.mysecurecloudhost.com ⭐ ⚠️ Not in zone NS records
A13.248.158.180🇺🇸 Amazon13.248.144.0/20
PTRa79764cc55c0ac9c0.awsglobalaccelerator.com
NSns2.mysecurecloudhost.com ⚠️ Not in zone NS records
A75.2.118.134🇺🇸 Amazon75.2.112.0/20
PTRabc65dd9a44b5332f.awsglobalaccelerator.com
NSns3.mysecurecloudhost.com ⚠️ Not in zone NS records
A76.223.26.245🇺🇸 Amazon76.223.16.0/20
PTRa79764cc55c0ac9c0.awsglobalaccelerator.com
NSns4.mysecurecloudhost.com ⚠️ Not in zone NS records
A99.83.147.209🇺🇸 Amazon99.83.144.0/20
PTRabc65dd9a44b5332f.awsglobalaccelerator.com
MXtestingforclient.com
A23.94.221.209🇺🇸 COLOCROSSING23.94.221.0/24 ColoCrossing
PTRkeycancelcom.guiran.me
SOAns1.mysecurecloudhost.comservers@mysecurecloudhost.com 2026-08-21 #17

com

MX for

Same first word

Previous names

Next names

DNS History

6 records (6 active, 0 former)

NSns1.mysecurecloudhost.comns2.mysecurecloudhost.comns3.mysecurecloudhost.comns4.mysecurecloudhost.comMXtestingforclient.comA23.94.221.209
NSns1.mysecurecloudhost.com2026-08-25 → 2026-09-04 · 2 obs
● 2026-08-25 15:53:12
● 2026-09-04 20:21:22
NSns2.mysecurecloudhost.com2026-08-25 → 2026-09-04 · 2 obs
● 2026-08-25 15:53:12
● 2026-09-04 20:21:22
NSns3.mysecurecloudhost.com2026-08-25 → 2026-09-04 · 2 obs
● 2026-08-25 15:53:12
● 2026-09-04 20:21:22
NSns4.mysecurecloudhost.com2026-08-25 → 2026-09-04 · 2 obs
● 2026-08-25 15:53:12
● 2026-09-04 20:21:22
MXtestingforclient.com2026-08-25 → 2026-09-04 · 2 obs
● 2026-08-25 15:53:12
● 2026-09-04 20:21:22
A23.94.221.2092026-08-25 → 2026-09-04 · 2 obs
● 2026-08-25 15:53:12
● 2026-09-04 20:21:22

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
testingforclient.comns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com4 records

✅ Authoritative Response

Server:99.83.147.209

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for testingforclient.com (unsigned zone)

⏱️ Timing

Total: 182ms | Queries: -

📄 Records

TypeCountSample Data
A123.94.221.209
MX1testingforclient.com (pri: 0)
SOA1ns1.mysecurecloudhost.com servers.mysecu

📌 Glue Records Collected

Total: 4

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

Analysis

Mail Server Role

testingforclient.com acts as its own mail server.

IP Addresses

testingforclient.com points to a single IP number: 23.94.221.209.

Additional host names — armourwallet.com, recentlyfindingsarah.com, thelosangelescalifornia.com and two others — share IP numbers with testingforclient.com.

Name Servers

testingforclient.com has four authoritative name servers: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and ns4.mysecurecloudhost.com.

At least some of testingforclient.com's name servers are shared with other domains, for example posty.com.py, lonestarartists.com, werrkflow.com and two more.

These name servers are often deployed together with the name servers ns1.a2hosting.com, ns2.a2hosting.com, ns3.a2hosting.com and ns4.a2hosting.com.

ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and ns4.mysecurecloudhost.com each resolve to one IP address: ns1.mysecurecloudhost.com resolves to 13.248.158.180, ns2.mysecurecloudhost.com resolves to 75.2.118.134, ns3.mysecurecloudhost.com resolves to 76.223.26.245 and ns4.mysecurecloudhost.com resolves to 99.83.147.209.

Mail Servers

testingforclient.com has a single mail server: testingforclient.com itself.

testingforclient.com resolves to 23.94.221.209 and no other IP number.