wpflow.com - dns.ninja
wpflow.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=1785169227 | ||||||
Subdomains
www.wpflow.com |
Same first word
Similar names
DNS History
14 records (11 active, 3 former)
●MXalt1.aspmx.l.google.com2015-08-22 → 2026-07-27 · 2 obs
● 2026-07-27 16:28:42
●MXalt2.aspmx.l.google.com2015-08-22 → 2026-07-27 · 2 obs
● 2026-07-27 16:28:42
●MXaspmx.l.google.com2015-08-22 → 2026-07-27 · 2 obs
● 2026-07-27 16:28:42
●MXaspmx2.googlemail.com2015-08-22 → 2026-07-27 · 2 obs
● 2026-07-27 16:28:42
●MXaspmx3.googlemail.com2015-08-22 → 2026-07-27 · 2 obs
● 2026-07-27 16:28:42
○A104.199.120.2132017-03-13 → 2017-03-13 · 3 obs
● 2017-03-13 03:59:54
○ 2026-07-27 16:28:42
●A167.71.87.812026-07-27 → 2026-07-27 · 2 obs
● 2026-07-27 16:28:42
○A45.33.60.1792015-08-22 → 2016-07-11 · 4 obs
● 2016-07-11 07:42:10
○ 2017-03-13 03:59:54
○ 2026-07-27 16:28:42
○CNAMEwpflow.wpengine.com2015-08-22 → 2017-03-13 · 3 obs
● 2017-03-13 03:59:54
○ 2026-07-27 16:28:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net, f.gtld-servers.net... | - |
| wpflow.com | ns1cmt.name.com, ns2nsy.name.com, ns3ghw.name.com, ns4cpw.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1cmt.name.com, ns2nsy.name.com, ns3ghw.name.com, ns4cpw.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for wpflow.com (unsigned zone)
⏱️ Timing
Total: 157ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 167.71.87.81 |
| NS | 4 | ns1cmt.name.com, ns2nsy.name.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 30)... |
| TXT | 3 | v=spf1 include:_spf.google.com include:h, google-site-verification=KcXG9j7r_3rRaF3... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1cmt.name.com, ns1cmt.name.com, ns2nsy.name.com...)
Analysis
Hierarchy
wpflow.com is the parent zone for www.wpflow.com.
IP Addresses
wpflow.com has exactly one IP address — 167.71.87.81.
Other host names share IP numbers with wpflow.com; www.wpflow.com is one such example.
Name Servers
Five name servers handle delegation for wpflow.com: ns1.name.com, ns1cmt.name.com, ns2nsy.name.com and two others.
wpflow.com partially shares its NS delegation with several other domains, including tunder365.info, thepml.net, aqvero.net and two others.
In DNS configurations, these name servers often share authority with ns4cpw.name.com, ns3ghw.name.com, ns1cnb.name.com and 7 other name servers.
Host names pointing to two IP addresses:
ns1.name.com maps to two IP addresses — 163.114.216.17 and 2a00:edc0:107::1.
ns1cmt.name.com maps to two IP addresses — 163.114.216.17 and 2a00:edc0:107::1.
ns2nsy.name.com maps to two IP addresses — 163.114.216.49 and 2402:cf80:107::1.
ns3ghw.name.com maps to two IP addresses — 163.114.217.17 and 2a00:edc0:107::49.
ns4cpw.name.com maps to two IP addresses — 163.114.217.49 and 2402:cf80:107::49.
These two host names — ns1.name.com and ns1cmt.name.com — each point to 2a00:edc0:107::1 IP addresses.
These two host names — ns1.name.com and ns1cmt.name.com — each point to 163.114.216.17 IP addresses.
Mail Servers
Mail for wpflow.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by wpflow.com are shared with other domains: ns500693.ns500699.ns500699.ns500693.ns500699.ns500588.ns500699.ns500588.ns500683.ns500693.ns500612.ns500632.ns500632.ns500632.dtrkdll.com, ns500765.ns500699.ns500693.ns500693.ns500693.ns500693.ns500699.ns500588.ns500693.ns500588.ns500699.ns500693.ns500693.ns500693.ns500683.ns500699.ns500602.dtrkdll.com, ns500758.ns500758.ns500735.ns500735.ns500735.ns500735.ns500576.ns500576.ns500708.ns500708.ns500698.ns500576.ns500708.ns500619.ns500576.ns500619.ns500619.trackreceptor.com and two others among them.
These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com maps to two IP addresses — 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com maps to two IP addresses — 142.251.163.27 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1b.
These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 108.177.123.26 IP addresses.