phinsecurity.com - dns.ninja
phinsecurity.com
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=1786151939 | ||||||
Subdomains
Same first word
phinsecurity.com |
DNS History
9 records (9 active, 0 former)
●NSns-cloud-c1.googledomains.com2026-02-19 → 2026-08-08 · 2 obs
● 2026-08-08 01:25:48
●NSns-cloud-c2.googledomains.com2026-02-19 → 2026-08-08 · 2 obs
● 2026-08-08 01:25:48
●NSns-cloud-c3.googledomains.com2026-02-19 → 2026-08-08 · 2 obs
● 2026-08-08 01:25:48
●NSns-cloud-c4.googledomains.com2026-02-19 → 2026-08-08 · 2 obs
● 2026-08-08 01:25:48
●MXalt1.aspmx.l.google.com2026-02-19 → 2026-08-08 · 2 obs
● 2026-08-08 01:25:48
●MXalt2.aspmx.l.google.com2026-02-19 → 2026-08-08 · 2 obs
● 2026-08-08 01:25:48
●MXaspmx.l.google.com2026-02-19 → 2026-08-08 · 2 obs
● 2026-08-08 01:25:48
●A199.60.103.1682026-02-19 → 2026-08-08 · 2 obs
● 2026-08-08 01:25:48
●A199.60.103.682026-02-19 → 2026-08-08 · 2 obs
● 2026-08-08 01:25:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net, g.gtld-servers.net... | - |
| phinsecurity.com | ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.32.108
NS records: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 483ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 199.60.103.68, 199.60.103.168 |
| NS | 4 | ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com... |
| MX | 3 | aspmx.l.google.com (pri: 1), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 9 | hubspot-developer-verification=Zjc2ZTdkO, MS=1BC26303DB734E9D6964BA59CF9C62FB00714... |
| SOA | 1 | ns-cloud-c1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-c1.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com...)
Analysis
Hierarchy
phinsecurity.com serves as the parent of relay.phinsecurity.com and www.phinsecurity.com.
IP Addresses
phinsecurity.com resolves to the IP addresses 199.60.103.68 and 199.60.103.168
ldm.la, aquera.com, sealsq.com plus two other host names have IP numbers in common with phinsecurity.com.
Name Servers
Four name servers handle the delegation for phinsecurity.com: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.
phinsecurity.com partially shares its NS delegation with several other domains, including theferm.net, seshadri.net, lcr.com.br and two others.
ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com each carry two IP addresses. ns-cloud-c1.googledomains.com has 216.239.32.108 and 2001:4860:4802:32::6c; ns-cloud-c2.googledomains.com has 216.239.34.108 and 2001:4860:4802:34::6c; ns-cloud-c3.googledomains.com has 216.239.36.108 and 2001:4860:4802:36::6c; ns-cloud-c4.googledomains.com has 216.239.38.108 and 2001:4860:4802:38::6c.
Mail Servers
phinsecurity.com uses three mail servers — aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
At least some of the mail servers used by phinsecurity.com are shared with other domains: ns500821.ns500794.ns500795.ns500794.ns500794.ns500821.ns500794.ns500821.ns500795.ns500795.ns500790.ns500795.lustypartnersfinder.com, ns500765.ns500699.ns500699.ns500734.ns500734.ns500699.ns500693.ns500588.ns500588.ns500588.ns500683.ns500612.ns500612.ns500110.dtrkdll.com, ns500699.ns500765.ns500734.ns500699.ns500734.ns500734.ns500588.ns500693.ns500683.ns500683.ns500588.ns500632.ns500612.ns500612.ns500578.ns500110.dtrkdll.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.
Three hostnames — aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com — each have two IP addresses: aspmx.l.google.com has 142.251.163.27 and 2607:f8b0:4004:c0b::1a, alt1.aspmx.l.google.com has 108.177.123.27 and 2800:3f0:4003:c0f::1a, and alt2.aspmx.l.google.com has 172.253.116.27 and 2a00:1450:400b:c02::1b.