hcscm.com - robtex.com
hcscm.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns3.afternic.com ⭐ | ||||||
| A | 97.74.98.65🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns3.afternic.com | ||||||
| NS | ns4.afternic.com | ||||||
| A | 173.201.66.65🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns4.namefind.com | ||||||
| NS | verification-xca45ox5qyba6vycrpoay7.ns101.verify.hn ⚠️ Not in zone NS records | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns3.afternic.comdns@jomax.net 2025-10-01 #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.netnstld@verisign-grs.com serial=1783515451 | ||||||
Same first word
Similar names
DNS History
9 records (5 active, 4 former)
○NSdns31.hichina.com2015-08-12 → 2017-10-17 · 4 obs
● 2015-08-12 17:39:46
● 2017-10-17 22:40:14
○ 2026-06-26 07:18:38
○ 2026-07-08 13:14:58
● 2017-10-17 22:40:14
○ 2026-06-26 07:18:38
○ 2026-07-08 13:14:58
○NSdns32.hichina.com2015-08-12 → 2017-10-17 · 4 obs
● 2015-08-12 17:39:46
● 2017-10-17 22:40:14
○ 2026-06-26 07:18:38
○ 2026-07-08 13:14:58
● 2017-10-17 22:40:14
○ 2026-06-26 07:18:38
○ 2026-07-08 13:14:58
●NSns3.afternic.com2026-06-26 → 2026-07-08 · 3 obs
○ 2017-10-17 22:40:14
● 2026-06-26 07:18:38
● 2026-07-08 13:14:58
● 2026-06-26 07:18:38
● 2026-07-08 13:14:58
●NSns4.afternic.com2026-06-26 → 2026-07-08 · 3 obs
○ 2017-10-17 22:40:14
● 2026-06-26 07:18:38
● 2026-07-08 13:14:58
● 2026-06-26 07:18:38
● 2026-07-08 13:14:58
●NSverification-xca45ox5qyba6vycrpoay7.ns101.verify.hn2026-06-26 → 2026-07-08 · 3 obs
○ 2017-10-17 22:40:14
● 2026-06-26 07:18:38
● 2026-07-08 13:14:58
● 2026-06-26 07:18:38
● 2026-07-08 13:14:58
○MXmxn.mxhichina.com2015-08-12 → 2017-10-17 · 4 obs
● 2015-08-12 17:39:46
● 2017-10-17 22:40:14
○ 2026-06-26 07:18:38
○ 2026-07-08 13:14:58
● 2017-10-17 22:40:14
○ 2026-06-26 07:18:38
○ 2026-07-08 13:14:58
○MXmxw.mxhichina.com2015-08-12 → 2017-10-17 · 4 obs
● 2015-08-12 17:39:46
● 2017-10-17 22:40:14
○ 2026-06-26 07:18:38
○ 2026-07-08 13:14:58
● 2017-10-17 22:40:14
○ 2026-06-26 07:18:38
○ 2026-07-08 13:14:58
●A13.248.169.482026-06-26 → 2026-07-08 · 2 obs
● 2026-06-26 07:18:38
● 2026-07-08 13:14:58
● 2026-07-08 13:14:58
●A76.223.54.1462026-06-26 → 2026-07-08 · 2 obs
● 2026-06-26 07:18:38
● 2026-07-08 13:14:58
● 2026-07-08 13:14:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net, h.gtld-servers.net... | - |
| hcscm.com | ns3.afternic.com, ns4.afternic.com, verification-xca45ox5qyba6vycrpoay7.ns101.verify.hn | 2 records |
✅ Authoritative Response
Server:97.74.98.65
NS records: ns3.afternic.com, ns4.afternic.com, verification-xca45ox5qyba6vycrpoay7.ns101.verify.hn
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for hcscm.com (unsigned zone)
⏱️ Timing
Total: 3593ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 13.248.169.48, 76.223.54.146 |
| NS | 2 | ns3.afternic.com, ns4.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns3.afternic.com dns.jomax.net |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns3.afternic.com, ns4.afternic.com)
Analysis
IP Addresses
hcscm.com resolves to the IP addresses 13.248.169.48 and 76.223.54.146
Name Servers
hcscm.com carries NS records delegating to ns3.afternic.com, ns4.afternic.com and verification-xca45ox5qyba6vycrpoay7.ns101.verify.hn.
ns3.afternic.com resolves to 97.74.98.65. ns4.afternic.com resolves to 173.201.66.65. Both host names point to a single IP number.