peercom.com - dns.ninja
peercom.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=1784213527 | ||||||
Subdomains
Same first word
peercom.com |
Similar names
DNS History
9 records (6 active, 3 former)
●NSns-cloud-a1.googledomains.com2026-02-15 → 2026-07-16 · 3 obs
● 2026-02-15 08:37:12
● 2026-07-16 14:53:06
●NSns-cloud-a2.googledomains.com2026-02-15 → 2026-07-16 · 3 obs
● 2026-02-15 08:37:12
● 2026-07-16 14:53:06
●NSns-cloud-a3.googledomains.com2026-02-15 → 2026-07-16 · 3 obs
● 2026-02-15 08:37:12
● 2026-07-16 14:53:06
●NSns-cloud-a4.googledomains.com2026-02-15 → 2026-07-16 · 3 obs
● 2026-02-15 08:37:12
● 2026-07-16 14:53:06
○NSns1.digitedge.com2015-08-18 → 2017-01-01 · 4 obs
● 2017-01-01 02:48:50
○ 2026-02-15 08:37:12
○ 2026-07-16 14:53:06
○NSnyns1.digitaledge.net2015-08-18 → 2017-01-01 · 4 obs
● 2017-01-01 02:48:50
○ 2026-02-15 08:37:12
○ 2026-07-16 14:53:06
○NSnyns2.digitaledge.net2015-08-18 → 2017-01-01 · 4 obs
● 2017-01-01 02:48:50
○ 2026-02-15 08:37:12
○ 2026-07-16 14:53:06
●MXmail.peercom.com2015-08-18 → 2026-07-16 · 2 obs
● 2026-07-16 14:53:06
●A208.74.201.2322015-08-18 → 2026-07-16 · 2 obs
● 2026-07-16 14:53:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, f.gtld-servers.net, c.gtld-servers.net, a.gtld-servers.net... | - |
| peercom.com | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.38.106
NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for peercom.com (unsigned zone)
⏱️ Timing
Total: 454ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 208.74.201.232 |
| NS | 4 | ns-cloud-a1.googledomains.com, ns-cloud-a4.googledomains.com... |
| MX | 1 | mail.peercom.com (pri: 10) |
| TXT | 6 | v=spf1 mx ip4:208.74.201.225 -all, vg594uv6q8btpqr695hgve2i95... |
| SOA | 1 | ns-cloud-a1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)
Analysis
Hierarchy
www.peercom.com and mail.peercom.com each fall under peercom.com as their parent domain.
IP Addresses
peercom.com resolves to just one IP address, 208.74.201.232.
Other host names, such as www.peercom.com, share IP numbers with peercom.com.
Name Servers
The NS records for peercom.com point to four name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.
peercom.com has at least partial name server overlap with other domains, such as handymanseo.com, bready.us, succeed-tokyo.com and two others.
It is common to find these name servers paired with the name servers ns1.mirusresearch.com.
ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com all point to exactly two IP numbers each: ns-cloud-a1.googledomains.com → 216.239.32.106 and 2001:4860:4802:32::6a; ns-cloud-a2.googledomains.com → 216.239.34.106 and 2001:4860:4802:34::6a; ns-cloud-a3.googledomains.com → 216.239.36.106 and 2001:4860:4802:36::6a; ns-cloud-a4.googledomains.com → 216.239.38.106 and 2001:4860:4802:38::6a.
Mail Servers
The sole mail server for peercom.com is mail.peercom.com.
mail.peercom.com resolves to a single IP number: 208.74.201.225.