packethacker.com - dns.ninja
packethacker.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 68.99.67.103🇺🇸 CCINET68.99.64.0/21 NETBLK-OKCBSHFC-68-99-64-0 | ||||||
| PTR | www.iwolfie.com | ||||||
| PTR | wsip-68-99-67-103.ok.ok.cox.net | ||||||
| NS | ns1.mydomain.com ⭐ | ||||||
| A | 172.64.52.99🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.mydomain.com | ||||||
| A | 172.64.53.76🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns3.mydomain.com ⚠️ Not in zone NS records | ||||||
| A | 172.64.52.99🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns4.mydomain.com ⚠️ Not in zone NS records | ||||||
| A | 172.64.53.76🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| MX | packethacker.com ⭐ | ||||||
| A | 68.99.67.103🇺🇸 CCINET68.99.64.0/21 NETBLK-OKCBSHFC-68-99-64-0 | ||||||
| PTR | www.iwolfie.com | ||||||
| PTR | wsip-68-99-67-103.ok.ok.cox.net | ||||||
| TXT | v=spf1 mx a ip4:68.99.67.103/32 -all | ||||||
| SOA | ns1.mydomain.comdnsadmin@mydomain.com 2020-12-04 #45 | ||||||
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=1786882719 | ||||||
MX for
packethacker.com |
Same first word
packethacker.com |
DNS History
8 records (6 active, 2 former)
●NSns1.mydomain.com2026-03-17 → 2026-08-16 · 3 obs
● 2026-03-17 21:01:30
● 2026-08-16 12:22:16
○NSns1.yourhostingaccount.com2015-07-22 → 2020-03-10 · 4 obs
● 2020-03-10 07:42:36
○ 2026-03-17 21:01:30
○ 2026-08-16 12:22:16
●NSns2.mydomain.com2026-03-17 → 2026-08-16 · 3 obs
● 2026-03-17 21:01:30
● 2026-08-16 12:22:16
○NSns2.yourhostingaccount.com2015-07-22 → 2020-03-10 · 4 obs
● 2020-03-10 07:42:36
○ 2026-03-17 21:01:30
○ 2026-08-16 12:22:16
●NSns3.mydomain.com2026-03-17 → 2026-08-16 · 3 obs
● 2026-03-17 21:01:30
● 2026-08-16 12:22:16
●NSns4.mydomain.com2026-03-17 → 2026-08-16 · 3 obs
● 2026-03-17 21:01:30
● 2026-08-16 12:22:16
●MXpackethacker.com2015-07-22 → 2026-08-16 · 2 obs
● 2026-08-16 12:22:16
●A68.99.67.1032015-07-22 → 2026-08-16 · 2 obs
● 2026-08-16 12:22:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net... | - |
| packethacker.com | ns1.mydomain.com, ns2.mydomain.com, ns3.mydomain.com, ns4.mydomain.com | 4 records |
✅ Authoritative Response
Server:172.64.52.99
NS records: ns1.mydomain.com, ns2.mydomain.com, ns3.mydomain.com, ns4.mydomain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for packethacker.com (unsigned zone)
⏱️ Timing
Total: 1864ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns2.mydomain.com, ns1.mydomain.com |
| TXT | 1 | v=spf1 mx a ip4:68.99.67.103/32 -all |
| SOA | 1 | ns1.mydomain.com dnsadmin.mydomain.com |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.mydomain.com, ns2.mydomain.com, ns3.mydomain.com...)
Analysis
Mail Server Role
The MX record for packethacker.com points back to packethacker.com — it is its own mail server.
IP Addresses
packethacker.com directs to one IP number, which is 68.99.67.103.
Other host names — mail.iwolfie.com, www.iwolfie.com, wsip-68-99-67-103.ok.ok.cox.net and iwolfie.com — share IP numbers with packethacker.com.
Name Servers
The domain packethacker.com is delegated to these four name servers: ns1.mydomain.com, ns2.mydomain.com, ns3.mydomain.com and ns4.mydomain.com.
At least some of packethacker.com's name servers are shared with other domains, for example imperialrh.com, ewingcarpet.com, dersongroup.com and two more.
These name servers tend to be deployed in combination with the name servers ns1.yourhostingaccount.com and ns2.yourhostingaccount.com.
ns1.mydomain.com, ns2.mydomain.com, ns3.mydomain.com and ns4.mydomain.com each point to exactly one IP address. ns1.mydomain.com directs to 172.64.52.99, ns2.mydomain.com directs to 172.64.53.76, ns3.mydomain.com directs to 172.64.52.99 and ns4.mydomain.com directs to 172.64.53.76. Two pairs share an IP: ns1.mydomain.com and ns3.mydomain.com share 172.64.52.99, and ns2.mydomain.com and ns4.mydomain.com share 172.64.53.76.
ns1.mydomain.com and ns3.mydomain.com are host names that each point to 172.64.52.99 IP addresses.
ns2.mydomain.com and ns4.mydomain.com are host names that each point to 172.64.53.76 IP addresses.
Mail Servers
The MX record for packethacker.com points to a single mail server: packethacker.com.
packethacker.com resolves to a single IP number: 68.99.67.103.