phinaz.com - robtex.com
phinaz.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=1784275097 | ||||||
Same first word
phinaz.com |
Similar names
zanphi.com |
panzhi.cn |
zainph.com |
zhipan.com |
apinhz.com |
hanzpi.com |
zaphin.com |
phinza.com |
panzhi.net |
zhipan.cn |
pianzh.com |
DNS History
13 records (8 active, 5 former)
●NSns.rackspace.com2007-08-14 → 2026-07-17 · 2 obs
● 2026-07-17 08:14:02
●NSns2.rackspace.com2007-08-14 → 2026-07-17 · 2 obs
● 2026-07-17 08:14:02
●MXalt1.aspmx.l.google.com2026-06-20 → 2026-07-17 · 3 obs
● 2026-06-20 23:23:12
● 2026-07-17 08:14:02
●MXalt2.aspmx.l.google.com2026-06-20 → 2026-07-17 · 3 obs
● 2026-06-20 23:23:12
● 2026-07-17 08:14:02
●MXalt3.aspmx.l.google.com2026-06-20 → 2026-07-17 · 3 obs
● 2026-06-20 23:23:12
● 2026-07-17 08:14:02
●MXalt4.aspmx.l.google.com2026-06-20 → 2026-07-17 · 3 obs
● 2026-06-20 23:23:12
● 2026-07-17 08:14:02
●MXaspmx.l.google.com2026-06-20 → 2026-07-17 · 3 obs
● 2026-06-20 23:23:12
● 2026-07-17 08:14:02
○MXmail.phinaz.com2007-08-14 → 2007-08-14 · 3 obs
○ 2015-06-20 11:29:38
○ 2026-07-17 08:14:02
○MXmx1.emailsrvr.com2015-06-20 → 2017-08-17 · 5 obs
● 2015-06-20 11:29:38
● 2017-08-17 21:23:16
○ 2026-06-20 23:23:12
○ 2026-07-17 08:14:02
○MXmx2.emailsrvr.com2015-06-20 → 2017-08-17 · 5 obs
● 2015-06-20 11:29:38
● 2017-08-17 21:23:16
○ 2026-06-20 23:23:12
○ 2026-07-17 08:14:02
●A209.61.176.322026-06-20 → 2026-07-17 · 3 obs
● 2026-06-20 23:23:12
● 2026-07-17 08:14:02
○A66.216.78.2202007-08-14 → 2007-08-14 · 3 obs
○ 2015-06-20 11:29:38
○ 2026-07-17 08:14:02
○A72.32.126.1532015-06-20 → 2017-08-17 · 5 obs
● 2015-06-20 11:29:38
● 2017-08-17 21:23:16
○ 2026-06-20 23:23:12
○ 2026-07-17 08:14:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| phinaz.com | ns2.rackspace.com, ns.rackspace.com | 2 records |
✅ Authoritative Response
Server:69.20.95.4
NS records: ns2.rackspace.com, ns.rackspace.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for phinaz.com (unsigned zone)
⏱️ Timing
Total: 206ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 209.61.176.32 |
| NS | 2 | ns.rackspace.com, ns2.rackspace.com |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=FXpwWWnEAn_n3oW, v=spf1 a mx include:mailseat.com ?all |
| SOA | 1 | ns.rackspace.com hostmaster.rackspace.co |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns2.rackspace.com, ns.rackspace.com)
Analysis
IP Addresses
phinaz.com directs to one IP number, which is 209.61.176.32.
Name Servers
phinaz.com has two authoritative name servers — ns2.rackspace.com and ns.rackspace.com.
phinaz.com has the same name server delegation as a number of other domains, such as sideshow.expert, seattlemedina.com, 51.130.104.in-addr.arpa and two more.
phinaz.com has at least partial name server overlap with other domains, such as abs.com.my, irff.us, clickdatelove.com and two others.
It is common to see these name servers used together with name servers dns1.stabletransit.com and dns2.stabletransit.com.
ns2.rackspace.com directs to 65.61.188.4 and ns.rackspace.com directs to 69.20.95.4; each host name points to exactly one IP number.
Mail Servers
Mail for phinaz.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
phinaz.com shares at least some of its mail servers with other domains — for example ns500671.ns500742.ns500742.ns500731.ns500704.ns500671.ns500742.ns500742.ns500678.ns500291.ns500671.lusty(0x736c7574)z.com, ns500731.ns500671.ns500671.ns500742.ns500742.ns500671.ns500731.ns500705.ns500704.ns500678.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500699.ns500734.ns500734.ns500693.ns500699.ns500699.ns500693.ns500699.ns500693.ns500699.ns500699.ns500588.ns500612.ns500588.ns500632.ns500632.ns500110.dtrkdll.com and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 4 more.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to 142.251.111.27 and 2607:f8b0:4004:c06::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.