pfnagel.com - robtex.com
pfnagel.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 160.16.140.142🇯🇵 SAKURA-B160.16.128.0/17 (TOKYO) SAKURA Internet // EAST JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan | ||||||
| PTR | tk2-406-44138.vs.sakura.ne.jp | ||||||
| NS | a.nsbream.net ⭐ | ||||||
| A | 133.167.112.252🇯🇵 SAKURA-C133.167.0.0/16 (OSAKA) SAKURA Internet // WEST JAPAN BACKBONE Grand Front Osaka Tower A 35F, 4-20 Ofukacho, Kita-ku, Osaka, Osaka 530-0011, Japan | ||||||
| PTR | os3-386-26248.vs.sakura.ne.jp | ||||||
| NS | b.nsbream.net | ||||||
| A | 160.16.114.125🇯🇵 SAKURA-B160.16.0.0/17 SAKURA Internet // EAST JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan | ||||||
| PTR | tk2-233-26121.vs.sakura.ne.jp | ||||||
| SOA | a.nsbream.netadmin@pfnagel.com serial=1638235442 | ||||||
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=1777165656 | ||||||
Same first word
pfnagel.com |
Similar names
DNS History
15 records (3 active, 12 former)
●NSa.nsbream.net2026-03-28 → 2026-04-26 · 3 obs
○ 2020-02-02 22:33:10
● 2026-03-28 13:38:54
● 2026-04-26 01:22:42
● 2026-03-28 13:38:54
● 2026-04-26 01:22:42
●NSb.nsbream.net2026-03-28 → 2026-04-26 · 3 obs
○ 2020-02-02 22:33:10
● 2026-03-28 13:38:54
● 2026-04-26 01:22:42
● 2026-03-28 13:38:54
● 2026-04-26 01:22:42
○NSdns1.name-services.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-03-15 05:38:10
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
○NSdns2.name-services.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-03-15 05:38:10
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
○NSdns3.name-services.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-03-15 05:38:10
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
○NSdns4.name-services.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-03-15 05:38:10
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
○NSdns5.name-services.com2020-02-02 → 2020-02-02 · 4 obs
○ 2017-03-15 05:38:10
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
○NSns1.claritytech.com2015-07-24 → 2017-03-15 · 4 obs
● 2015-07-24 22:17:40
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
○NSns2.claritytech.com2015-07-24 → 2017-03-15 · 4 obs
● 2015-07-24 22:17:40
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
○MXmail-filter.claritytech.com2015-07-24 → 2017-03-15 · 4 obs
● 2015-07-24 22:17:40
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
○MXmail-filter1.claritytech.com2015-07-24 → 2017-03-15 · 4 obs
● 2015-07-24 22:17:40
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
○MXmail-filter2.claritytech.com2015-07-24 → 2017-03-15 · 4 obs
● 2015-07-24 22:17:40
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
●A160.16.140.1422026-03-28 → 2026-04-26 · 3 obs
○ 2020-02-02 22:33:10
● 2026-03-28 13:38:54
● 2026-04-26 01:22:42
● 2026-03-28 13:38:54
● 2026-04-26 01:22:42
○A66.170.31.2222015-07-24 → 2017-03-15 · 4 obs
● 2015-07-24 22:17:40
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
● 2017-03-15 05:38:10
○ 2020-02-02 22:33:10
○ 2026-04-26 01:22:42
○A91.195.240.1032020-02-02 → 2020-02-02 · 4 obs
○ 2017-03-15 05:38:10
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
● 2020-02-02 22:33:10
○ 2026-03-28 13:38:54
○ 2026-04-26 01:22:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, m.gtld-servers.net, e.gtld-servers.net, g.gtld-servers.net... | - |
| pfnagel.com | a.nsbream.net, b.nsbream.net | - |
✅ Authoritative Response
Server:160.16.114.125
NS records: a.nsbream.net, b.nsbream.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for pfnagel.com (unsigned zone)
⏱️ Timing
Total: 914ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 160.16.140.142 |
| NS | 2 | a.nsbream.net, b.nsbream.net |
| SOA | 1 | a.nsbream.net admin.pfnagel.com |
Analysis
IP Addresses
pfnagel.com resolves to one IP number: 160.16.140.142.
Other host names for instance acceptcoverage.com and tk2-406-44138.vs.sakura.ne.jp share IP numbers with pfnagel.com.
Name Servers
pfnagel.com's delegation uses two name servers: a.nsbream.net and b.nsbream.net.
pfnagel.com uses the same name server setup as other domains, such as boutiquegreek.com, reformasobrasmad.com, williamtraore.com, tameronsgarden.com and su-chef.com.
Host names with a single IP address: a.nsbream.net points to 133.167.112.252; b.nsbream.net points to 160.16.114.125.