wpgeocode.com - dns.ninja
wpgeocode.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=1783766262 | ||||||
Same first word
wpgeocode.com |
DNS History
7 records (7 active, 0 former)
●NSns01.domaincontrol.com2015-06-18 → 2026-07-11 · 2 obs
● 2026-07-11 10:54:48
●NSns02.domaincontrol.com2015-06-18 → 2026-07-11 · 2 obs
● 2026-07-11 10:54:48
●MXalt1.aspmx.l.google.com2015-06-18 → 2026-07-11 · 2 obs
● 2026-07-11 10:54:48
●MXalt2.aspmx.l.google.com2015-06-18 → 2026-07-11 · 2 obs
● 2026-07-11 10:54:48
●MXaspmx.l.google.com2015-06-18 → 2026-07-11 · 2 obs
● 2026-07-11 10:54:48
●MXaspmx2.googlemail.com2015-06-18 → 2026-07-11 · 2 obs
● 2026-07-11 10:54:48
●A54.243.54.2032015-06-18 → 2026-07-11 · 2 obs
● 2026-07-11 10:54:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| wpgeocode.com | ns01.domaincontrol.com, ns02.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.68.1
NS records: ns01.domaincontrol.com, ns02.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for wpgeocode.com (unsigned zone)
⏱️ Timing
Total: 260ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 54.243.54.203 |
| NS | 2 | ns01.domaincontrol.com, ns02.domaincontrol.com |
| MX | 4 | alt1.aspmx.l.google.com (pri: 0), alt2.aspmx.l.google.com (pri: 10)... |
| SOA | 1 | ns01.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns01.domaincontrol.com, ns01.domaincontrol.com, ns02.domaincontrol.com...)
Analysis
IP Addresses
wpgeocode.com resolves to just one IP address, 54.243.54.203.
Host names like ec2-54-243-54-203.compute-1.amazonaws.com are further examples that share IP numbers with wpgeocode.com.
Name Servers
Two name servers handle the delegation for wpgeocode.com: ns01.domaincontrol.com and ns02.domaincontrol.com.
wpgeocode.com shares its NS records with other domains, for example vitofl.com, dimarzio.nyc, totmusicstudio.net and two others.
ns01.domaincontrol.com and ns02.domaincontrol.com both carry two IP addresses. The A records for ns01.domaincontrol.com are 97.74.100.1 and 2603:5:2140::1; the A records for ns02.domaincontrol.com are 173.201.68.1 and 2603:5:2240::1.
Mail Servers
Mail for wpgeocode.com is handled by four mail servers: aspmx2.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
There is at least a partial MX overlap between wpgeocode.com and other domains, including fiseimex.com, firris.com, ns500754.ns500742.ns500731.ns500731.ns500742.ns500671.ns500742.ns500731.ns500688.ns500678.ns500649.ns500666.lustychickser.com and two others.
These mail servers frequently co-occur with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx3.googlemail.com and two others.
The hostnames aspmx2.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com each resolve to a pair of IP numbers — aspmx2.googlemail.com to 108.177.123.27 and 2800:3f0:4003:c0f::1a; aspmx.l.google.com to 142.251.179.26 and 2607:f8b0:4004:c29::1a; alt1.aspmx.l.google.com to 108.177.123.27 and 2800:3f0:4003:c0f::1b; alt2.aspmx.l.google.com to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 108.177.123.27 IP addresses.