p2forge.com - dns.ninja
p2forge.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 20.118.56.74🇺🇸 Microsoft20.64.0.0/10 | ||||||
| NS | ns1-02.azure-dns.com ⭐ | ||||||
| A | 2603:1061:0:700::2🇺🇸 Microsoft2603:1000::/25 MICROSOFT | ||||||
| PTR | ns1-02.azure-dns.com | ||||||
| A | 13.107.236.2🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns1-02.azure-dns.com | ||||||
| NS | ns2-02.azure-dns.net | ||||||
| A | 2620:1ec:8ec:700::2🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns2-02.azure-dns.net | ||||||
| A | 150.171.21.2🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-02.azure-dns.net | ||||||
| NS | ns3-02.azure-dns.org | ||||||
| A | 2a01:111:4000:700::2🇬🇧 Microsoft2a01:111:4000::/36 | ||||||
| PTR | ns3-02.azure-dns.org | ||||||
| A | 204.14.183.2🇺🇸 Microsoft204.14.180.0/22 | ||||||
| PTR | ns3-02.azure-dns.org | ||||||
| NS | ns4-02.azure-dns.info | ||||||
| A | 2620:1ec:bda:700::2🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns4-02.azure-dns.info | ||||||
| A | 208.84.5.2🇺🇸 Microsoft208.84.0.0/21 MICROSOFT | ||||||
| PTR | ns4-02.azure-dns.info | ||||||
| SOA | ns1-02.azure-dns.comazuredns-hostmaster@microsoft.com serial=1 | ||||||
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=1786675374 | ||||||
Same first word
p2forge.com |
DNS History
24 records (5 active, 19 former)
○NSdns1.name-services.com2015-07-16 → 2017-02-05 · 4 obs
● 2017-02-05 00:58:18
○ 2019-02-21 11:11:08
○ 2026-08-14 03:01:34
○NSdns1.registrar-servers.com2019-02-21 → 2019-02-21 · 4 obs
● 2019-02-21 11:11:08
○ 2026-08-13 02:11:26
○ 2026-08-14 03:01:34
○NSdns2.name-services.com2015-07-16 → 2017-02-05 · 4 obs
● 2017-02-05 00:58:18
○ 2019-02-21 11:11:08
○ 2026-08-14 03:01:34
○NSdns2.registrar-servers.com2019-02-21 → 2019-02-21 · 4 obs
● 2019-02-21 11:11:08
○ 2026-08-13 02:11:26
○ 2026-08-14 03:01:34
○NSdns3.name-services.com2015-07-16 → 2017-02-05 · 4 obs
● 2017-02-05 00:58:18
○ 2019-02-21 11:11:08
○ 2026-08-14 03:01:34
○NSdns4.name-services.com2015-07-16 → 2017-02-05 · 4 obs
● 2017-02-05 00:58:18
○ 2019-02-21 11:11:08
○ 2026-08-14 03:01:34
○NSdns5.name-services.com2015-07-16 → 2017-02-05 · 4 obs
● 2017-02-05 00:58:18
○ 2019-02-21 11:11:08
○ 2026-08-14 03:01:34
●NSns1-02.azure-dns.com2026-08-13 → 2026-08-14 · 3 obs
● 2026-08-13 02:11:26
● 2026-08-14 03:01:34
●NSns2-02.azure-dns.net2026-08-13 → 2026-08-14 · 3 obs
● 2026-08-13 02:11:26
● 2026-08-14 03:01:34
●NSns3-02.azure-dns.org2026-08-13 → 2026-08-14 · 3 obs
● 2026-08-13 02:11:26
● 2026-08-14 03:01:34
●NSns4-02.azure-dns.info2026-08-13 → 2026-08-14 · 3 obs
● 2026-08-13 02:11:26
● 2026-08-14 03:01:34
○MXeforward1.registrar-servers.com2019-02-21 → 2019-02-21 · 4 obs
● 2019-02-21 11:11:08
○ 2026-08-13 02:11:26
○ 2026-08-14 03:01:34
○MXeforward2.registrar-servers.com2019-02-21 → 2019-02-21 · 4 obs
● 2019-02-21 11:11:08
○ 2026-08-13 02:11:26
○ 2026-08-14 03:01:34
○MXeforward3.registrar-servers.com2019-02-21 → 2019-02-21 · 4 obs
● 2019-02-21 11:11:08
○ 2026-08-13 02:11:26
○ 2026-08-14 03:01:34
○MXeforward4.registrar-servers.com2019-02-21 → 2019-02-21 · 4 obs
● 2019-02-21 11:11:08
○ 2026-08-13 02:11:26
○ 2026-08-14 03:01:34
○MXeforward5.registrar-servers.com2019-02-21 → 2019-02-21 · 4 obs
● 2019-02-21 11:11:08
○ 2026-08-13 02:11:26
○ 2026-08-14 03:01:34
○MXeforwardct.name-services.com2015-07-16 → 2017-02-05 · 4 obs
● 2017-02-05 00:58:18
○ 2019-02-21 11:11:08
○ 2026-08-14 03:01:34
○MXeforwardct2.name-services.com2015-07-16 → 2017-02-05 · 4 obs
● 2017-02-05 00:58:18
○ 2019-02-21 11:11:08
○ 2026-08-14 03:01:34
○MXeforwardct3.name-services.com2015-07-16 → 2017-02-05 · 4 obs
● 2017-02-05 00:58:18
○ 2019-02-21 11:11:08
○ 2026-08-14 03:01:34
○A192.64.119.622019-02-21 → 2019-02-21 · 4 obs
● 2019-02-21 11:11:08
○ 2026-08-13 02:11:26
○ 2026-08-14 03:01:34
●A20.118.56.742026-08-13 → 2026-08-14 · 3 obs
● 2026-08-13 02:11:26
● 2026-08-14 03:01:34
○A98.124.198.12015-07-16 → 2015-07-16 · 3 obs
○ 2017-02-05 00:58:18
○ 2026-08-14 03:01:34
○A98.124.199.12015-07-16 → 2015-07-16 · 3 obs
○ 2015-11-18 21:42:12
○ 2026-08-14 03:01:34
○A98.124.199.662015-11-18 → 2017-02-05 · 5 obs
● 2015-11-18 21:42:12
● 2017-02-05 00:58:18
○ 2019-02-21 11:11:08
○ 2026-08-14 03:01:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, h.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net... | - |
| p2forge.com | ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info | 2 records |
✅ Authoritative Response
Server:208.84.5.2
NS records: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for p2forge.com (unsigned zone)
⏱️ Timing
Total: 128ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 20.118.56.74 |
| NS | 4 | ns1-02.azure-dns.com, ns2-02.azure-dns.net... |
| SOA | 1 | ns1-02.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-02.azure-dns.com, ns1-02.azure-dns.com)
Analysis
IP Addresses
p2forge.com has exactly one IP address — 20.118.56.74.
mexicohunts.com, andesonline.com, useheicflow.com plus two other host names have IP numbers in common with p2forge.com.
Name Servers
Four name servers handle the delegation for p2forge.com: ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.
The name servers of p2forge.com overlap at least partially with those of other domains — among them igotim.com, diaphane-one.com, microsftinternetexplorer.com and two more.
Each of the four hosts ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org has two IP addresses. ns1-02.azure-dns.com points to 13.107.236.2 and 2603:1061:0:700::2. ns4-02.azure-dns.info points to 208.84.5.2 and 2620:1ec:bda:700::2. ns2-02.azure-dns.net points to 150.171.21.2 and 2620:1ec:8ec:700::2. ns3-02.azure-dns.org points to 204.14.183.2 and 2a01:111:4000:700::2.