peercom.com - robtex.com
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=1784871832 | ||||||
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-24 · 3 obs
● 2026-02-15 08:37:12
● 2026-07-24 05:46:52
●NSns-cloud-a2.googledomains.com2026-02-15 → 2026-07-24 · 3 obs
● 2026-02-15 08:37:12
● 2026-07-24 05:46:52
●NSns-cloud-a3.googledomains.com2026-02-15 → 2026-07-24 · 3 obs
● 2026-02-15 08:37:12
● 2026-07-24 05:46:52
●NSns-cloud-a4.googledomains.com2026-02-15 → 2026-07-24 · 3 obs
● 2026-02-15 08:37:12
● 2026-07-24 05:46:52
○NSns1.digitedge.com2015-08-18 → 2017-01-01 · 4 obs
● 2017-01-01 02:48:50
○ 2026-02-15 08:37:12
○ 2026-07-24 05:46:52
○NSnyns1.digitaledge.net2015-08-18 → 2017-01-01 · 4 obs
● 2017-01-01 02:48:50
○ 2026-02-15 08:37:12
○ 2026-07-24 05:46:52
○NSnyns2.digitaledge.net2015-08-18 → 2017-01-01 · 4 obs
● 2017-01-01 02:48:50
○ 2026-02-15 08:37:12
○ 2026-07-24 05:46:52
●MXmail.peercom.com2015-08-18 → 2026-07-24 · 2 obs
● 2026-07-24 05:46:52
●A208.74.201.2322015-08-18 → 2026-07-24 · 2 obs
● 2026-07-24 05:46:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net, d.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: 357ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 208.74.201.232 |
| NS | 4 | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com... |
| MX | 1 | mail.peercom.com (pri: 10) |
| TXT | 6 | 21vgmqdcunc9vdv7e8eodbnpif, google-site-verification=CC8mxJuHw3OJAsl... |
| 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 are both subdomains of peercom.com.
IP Addresses
peercom.com resolves to one IP address: 208.74.201.232.
Host names like www.peercom.com are further examples that share IP numbers with peercom.com.
Name Servers
The authoritative name servers for peercom.com are ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.
At least some of peercom.com's name servers are shared with other domains, for example handymanseo.com, bready.us, succeed-tokyo.com and two more.
These name servers tend to be deployed in combination with the name servers ns1.mirusresearch.com and ns2.mir.us.
Four hostnames, each resolving to a pair of IP addresses: ns-cloud-a1.googledomains.com directs to 216.239.32.106 and 2001:4860:4802:32::6a; ns-cloud-a2.googledomains.com directs to 216.239.34.106 and 2001:4860:4802:34::6a; ns-cloud-a3.googledomains.com directs to 216.239.36.106 and 2001:4860:4802:36::6a; ns-cloud-a4.googledomains.com directs to 216.239.38.106 and 2001:4860:4802:38::6a.
Mail Servers
Mail for peercom.com is handled by a single mail server, mail.peercom.com.
mail.peercom.com carries a single IP number, which is 208.74.201.225.