petermanphc.com - dns.ninja
petermanphc.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=1785287147 | ||||||
Same first word
petermanphc.com |
Similar names
DNS History
9 records (8 active, 1 former)
●NSns35.domaincontrol.com2015-08-01 → 2026-07-29 · 2 obs
● 2026-07-29 01:19:10
●NSns36.domaincontrol.com2015-08-01 → 2026-07-29 · 2 obs
● 2026-07-29 01:19:10
●MXalt1.aspmx.l.google.com2015-08-01 → 2026-07-29 · 2 obs
● 2026-07-29 01:19:10
●MXalt2.aspmx.l.google.com2015-08-01 → 2026-07-29 · 2 obs
● 2026-07-29 01:19:10
●MXaspmx.l.google.com2015-08-01 → 2026-07-29 · 2 obs
● 2026-07-29 01:19:10
●MXaspmx2.googlemail.com2015-08-01 → 2026-07-29 · 2 obs
● 2026-07-29 01:19:10
●MXaspmx3.googlemail.com2015-08-01 → 2026-07-29 · 2 obs
● 2026-07-29 01:19:10
●A159.203.73.732026-03-27 → 2026-07-29 · 3 obs
● 2026-03-27 02:37:54
● 2026-07-29 01:19:10
○A204.197.248.152015-08-01 → 2017-06-26 · 4 obs
● 2017-06-26 02:43:22
○ 2026-03-27 02:37:54
○ 2026-07-29 01:19:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net... | - |
| petermanphc.com | ns35.domaincontrol.com, ns36.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.75.18
NS records: ns35.domaincontrol.com, ns36.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for petermanphc.com (unsigned zone)
⏱️ Timing
Total: 292ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 159.203.73.73 |
| NS | 2 | ns35.domaincontrol.com, ns36.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 3 | google-site-verification=hXtjzU4dHUD8UnY, v=spf1 include:_spf.google.com ~all... |
| SOA | 1 | ns35.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns35.domaincontrol.com, ns35.domaincontrol.com, ns36.domaincontrol.com...)
Analysis
IP Addresses
petermanphc.com directs to one IP number, which is 159.203.73.73.
Name Servers
petermanphc.com uses two name servers for its delegation: ns35.domaincontrol.com and ns36.domaincontrol.com.
petermanphc.com has the same name server delegation as a number of other domains, such as myractools.co.uk, kamalrestaurant.co.uk, lilbigheroes.com and two more.
The two host names ns35.domaincontrol.com and ns36.domaincontrol.com each have a pair of IP addresses: ns35.domaincontrol.com has 97.74.107.18 and 2603:5:21b1::12, and ns36.domaincontrol.com has 173.201.75.18 and 2603:5:22b1::12.
Mail Servers
Five mail servers handle petermanphc.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
petermanphc.com shares at least some of its mail servers with other domains — for example despencer.com, ns500742.ns500742.ns500754.ns500754.ns500704.ns500671.ns500671.ns500291.ns500649.ns500649.ns500291.ns500131.lustychickser.com, ns500599.ns500599.ns500599.ns500599.ns500724.ns500599.ns500724.ns500737.ns500737.ns500724.ns500697.ns500697.ns500631.www.yummyflingsfinder.com and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com directs traffic to 108.177.123.27 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 64.233.180.26 and 2607:f8b0:4004:c25::1b.
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::1b.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.