hcc.ps - robtex.com
hcc.ps
ps
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns2.pnina.ps ⭐ | ||||||
| NS | bilal.pnina.ps | ||||||
| NS | fork.sth.dnsnode.net ⚠️ Not in parent delegation | ||||||
| NS | ns1.pnina.ps | ||||||
| NS | ote.pnina.ps ⚠️ Not in parent delegation | ||||||
| NS | ps-ns.anycast.pch.net ⚠️ Not in parent delegation | ||||||
| NS | ps.cctld.authdns.ripe.net ⚠️ Not in parent delegation | ||||||
| NS | rip.psg.com ⚠️ Not in parent delegation | ||||||
| TXT | Generation Time: 1784959312 | ||||||
| SOA | ns2.pnina.pssys@pnina.ps 2026-07-25 #4 | ||||||
Same first word
Similar names
DNS History
13 records (11 active, 2 former)
●NScortney.ns.cloudflare.com2026-06-23 → 2026-07-25 · 2 obs
● 2026-07-25 18:15:22
●NSrajeev.ns.cloudflare.com2026-06-23 → 2026-07-25 · 2 obs
● 2026-07-25 18:15:22
●MXalt1.aspmx.l.google.com2026-06-23 → 2026-07-25 · 2 obs
● 2026-07-25 18:15:22
●MXalt2.aspmx.l.google.com2026-06-23 → 2026-07-25 · 2 obs
● 2026-07-25 18:15:22
●MXalt3.aspmx.l.google.com2026-06-23 → 2026-07-25 · 2 obs
● 2026-07-25 18:15:22
●MXalt4.aspmx.l.google.com2026-06-23 → 2026-07-25 · 2 obs
● 2026-07-25 18:15:22
●MXaspmx.l.google.com2026-06-23 → 2026-07-25 · 2 obs
● 2026-07-25 18:15:22
●A104.21.61.2082026-06-23 → 2026-07-25 · 2 obs
● 2026-07-25 18:15:22
●A172.67.214.1412026-06-23 → 2026-07-25 · 2 obs
● 2026-07-25 18:15:22
○A2606:4700:3030::6815:3dd02026-06-23 → 2026-06-23 · 3 obs
○ 2026-07-08 22:57:10
○ 2026-07-25 18:15:22
●A2606:4700:3030::ac43:d68d2026-07-08 → 2026-07-25 · 3 obs
● 2026-07-08 22:57:10
● 2026-07-25 18:15:22
○A2606:4700:3033::ac43:d68d2026-06-23 → 2026-06-23 · 3 obs
○ 2026-07-08 22:57:10
○ 2026-07-25 18:15:22
●A2606:4700:3035::6815:3dd02026-07-08 → 2026-07-25 · 3 obs
● 2026-07-08 22:57:10
● 2026-07-25 18:15:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ps | ns1.pnina.ps, bilal.pnina.ps | - |
| hcc.ps | cortney.ns.cloudflare.com, rajeev.ns.cloudflare.com | - |
✅ Authoritative Response
Server:172.64.33.224
NS records: cortney.ns.cloudflare.com, rajeev.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ps (unsigned zone)
⏱️ Timing
Total: 2180ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 104.21.61.208, 172.67.214.141 |
| AAAA | 2 | 2606:4700:3030::ac43:d68d, 2606:4700:3035::6815:3dd0 |
| NS | 2 | cortney.ns.cloudflare.com, rajeev.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 4 | google-site-verification=1a7Zt0ycMDn5T0_, google-site-verification=Lggju-9LrWHxNUj... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | cortney.ns.cloudflare.com dns.cloudflare |
Analysis
IP Addresses
hcc.ps points to the four IP addresses 104.21.61.208, 172.67.214.141, 2606:4700:3030::ac43:d68d and 2606:4700:3035::6815:3dd0.
filterl.com, ionnorfolk.com, bwof.cn plus two other host names have IP numbers in common with hcc.ps.
Name Servers
Two name servers handle the delegation for hcc.ps: cortney.ns.cloudflare.com and rajeev.ns.cloudflare.com.
The name server configuration of hcc.ps is shared with other domains, for instance browniespain.com, linux-destek.com, chairesearchlab.com and two others.
There is at least partial name server overlap between hcc.ps and other domains — camillaguerra.com, josephsegal.com, kixdrinks.com and two more among them.
These name servers frequently co-occur with the name servers sreeni.ns.cloudflare.com and rustam.ns.cloudflare.com.
Hosts with 6 IP addresses each:
cortney.ns.cloudflare.com resolves to 108.162.192.87, 172.64.32.87 and 173.245.58.87 among others, with 3 other IP addresses in total.
rajeev.ns.cloudflare.com resolves to 108.162.193.224, 172.64.33.224 and 173.245.59.224 among others, with 3 other IP addresses in total.
Mail Servers
hcc.ps has five mail servers, which are 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 hcc.ps are shared with other domains: ns500759.ns500758.ns500758.ns500698.ns500736.ns500736.ns500736.ns500736.ns500708.ns500708.ns500619.ns500576.ns500576.ns500576.trackreceptor.com, ns500671.ns500754.ns500742.ns500754.ns500671.ns500705.ns500671.ns500688.ns500688.ns500291.ns500688.ns500678.tenderladiesbz.com, ns500742.ns500742.ns500731.ns500671.ns500731.ns500671.ns500688.ns500671.ns500671.ns500688.ns500671.ns500291.ns500649.ns500153.tenderladiesbz.com and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt1.aspmx.l.google.com resolves to two addresses: 142.250.102.27 and 2a00:1450:4025:402::1b.
alt2.aspmx.l.google.com resolves to two addresses: 192.178.213.26 and 2a00:1450:4013:c1e::1a.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1b.
aspmx.l.google.com along with alt3.aspmx.l.google.com each resolve to 2a00:1450:4009:c0f::1b IP addresses.
aspmx.l.google.com along with alt3.aspmx.l.google.com each resolve to 192.178.223.26 IP addresses.