pgcm.com - dns.ninja
pgcm.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=1782760941 | ||||||
Same first word
Similar names
DNS History
10 records (7 active, 3 former)
●NSdns1.registrar-servers.com2015-08-16 → 2026-06-29 · 2 obs
● 2026-06-29 19:32:36
●NSdns2.registrar-servers.com2015-08-16 → 2026-06-29 · 2 obs
● 2026-06-29 19:32:36
○NSdns3.registrar-servers.com2015-08-16 → 2016-06-13 · 4 obs
● 2016-06-13 23:22:08
○ 2017-02-08 00:36:22
○ 2026-06-29 19:32:36
○NSdns4.registrar-servers.com2015-08-16 → 2016-06-13 · 4 obs
● 2016-06-13 23:22:08
○ 2017-02-08 00:36:22
○ 2026-06-29 19:32:36
○NSdns5.registrar-servers.com2015-08-16 → 2016-06-13 · 4 obs
● 2016-06-13 23:22:08
○ 2017-02-08 00:36:22
○ 2026-06-29 19:32:36
●MXalt1.aspmx.l.google.com2015-08-16 → 2026-06-29 · 2 obs
● 2026-06-29 19:32:36
●MXalt2.aspmx.l.google.com2015-08-16 → 2026-06-29 · 2 obs
● 2026-06-29 19:32:36
●MXaspmx.l.google.com2015-08-16 → 2026-06-29 · 2 obs
● 2026-06-29 19:32:36
●MXaspmx2.googlemail.com2015-08-16 → 2026-06-29 · 2 obs
● 2026-06-29 19:32:36
●MXaspmx3.googlemail.com2015-08-16 → 2026-06-29 · 2 obs
● 2026-06-29 19:32:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| pgcm.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for pgcm.com (unsigned zone)
⏱️ Timing
Total: 218ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
Name Servers
pgcm.com uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.
pgcm.com shares its NS records with other domains, for example laverinto.com, iitoto.com, hwextreme.com and two others.
The name servers of pgcm.com overlap at least partially with those of other domains — among them nerally.com, fldna.co, rac2go.net and two more.
The name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com are commonly seen alongside these name servers.
The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
pgcm.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between pgcm.com and other domains, including metherapynyc.com, ns500821.ns500821.ns500821.ns500794.ns500794.ns500821.ns500821.ns500795.ns500795.ns500794.ns500821.ns500795.ns500795.ns500790.ns500795.lustypartnersfinder.com, ns500759.ns500758.ns500698.ns500758.ns500736.ns500735.ns500735.ns500735.ns500735.ns500735.ns500736.ns500698.ns500686.ns500576.ns500619.trackreceptor.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 172.253.63.27 and 2607:f8b0:4004:c1f::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.