whyrepipe.com - dns.ninja
whyrepipe.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=1784872017 | ||||||
Subdomains
Same first word
whyrepipe.com |
DNS History
23 records (5 active, 18 former)
○NSalina.ns.cloudflare.com2026-02-15 → 2026-04-07 · 5 obs
● 2026-02-15 14:53:16
● 2026-04-07 05:23:40
○ 2026-04-08 22:41:42
○ 2026-07-24 05:51:00
●NSernest.ns.cloudflare.com2026-02-15 → 2026-07-24 · 3 obs
● 2026-02-15 14:53:16
● 2026-07-24 05:51:00
○NSns1.namebrightdns.com2018-07-29 → 2018-07-29 · 4 obs
● 2018-07-29 01:03:40
○ 2026-02-15 14:53:16
○ 2026-07-24 05:51:00
○NSns2.namebrightdns.com2018-07-29 → 2018-07-29 · 4 obs
● 2018-07-29 01:03:40
○ 2026-02-15 14:53:16
○ 2026-07-24 05:51:00
○NSns45.domaincontrol.com2015-08-09 → 2017-02-07 · 4 obs
● 2017-02-07 21:52:48
○ 2018-07-29 01:03:40
○ 2026-07-24 05:51:00
○NSns46.domaincontrol.com2015-08-09 → 2017-02-07 · 4 obs
● 2017-02-07 21:52:48
○ 2018-07-29 01:03:40
○ 2026-07-24 05:51:00
●NSns63.domaincontrol.com2026-04-06 → 2026-07-24 · 3 obs
● 2026-04-06 05:19:46
● 2026-07-24 05:51:00
●NSns64.domaincontrol.com2026-04-06 → 2026-07-24 · 3 obs
● 2026-04-06 05:19:46
● 2026-07-24 05:51:00
○MXmailstore1.secureserver.net2015-08-09 → 2017-02-07 · 4 obs
● 2017-02-07 21:52:48
○ 2018-07-29 01:03:40
○ 2026-07-24 05:51:00
○MXsmtp.secureserver.net2015-08-09 → 2017-02-07 · 4 obs
● 2017-02-07 21:52:48
○ 2018-07-29 01:03:40
○ 2026-07-24 05:51:00
●MXwhyrepipe-com.mail.protection.outlook.com2026-02-15 → 2026-07-24 · 3 obs
● 2026-02-15 14:53:16
● 2026-07-24 05:51:00
○A104.26.0.992026-02-15 → 2026-03-24 · 5 obs
● 2026-02-15 14:53:16
● 2026-03-24 10:18:42
○ 2026-03-29 23:27:48
○ 2026-07-24 05:51:00
○A104.26.1.992026-02-15 → 2026-03-24 · 5 obs
● 2026-02-15 14:53:16
● 2026-03-24 10:18:42
○ 2026-03-29 23:27:48
○ 2026-07-24 05:51:00
○A15.197.225.1282026-04-06 → 2026-04-07 · 5 obs
● 2026-04-06 05:19:46
● 2026-04-07 05:23:40
○ 2026-04-08 22:41:42
○ 2026-07-24 05:51:00
○A172.67.74.422026-02-15 → 2026-03-24 · 5 obs
● 2026-02-15 14:53:16
● 2026-03-24 10:18:42
○ 2026-03-29 23:27:48
○ 2026-07-24 05:51:00
●A198.202.211.12026-05-23 → 2026-07-24 · 3 obs
● 2026-05-23 20:49:32
● 2026-07-24 05:51:00
○A2606:4700:20::681a:1632026-02-15 → 2026-03-24 · 5 obs
● 2026-02-15 14:53:16
● 2026-03-24 10:18:42
○ 2026-03-29 23:27:48
○ 2026-07-24 05:51:00
○A2606:4700:20::681a:632026-02-15 → 2026-03-24 · 5 obs
● 2026-02-15 14:53:16
● 2026-03-24 10:18:42
○ 2026-03-29 23:27:48
○ 2026-07-24 05:51:00
○A2606:4700:20::ac43:4a2a2026-02-15 → 2026-03-24 · 5 obs
● 2026-02-15 14:53:16
● 2026-03-24 10:18:42
○ 2026-03-29 23:27:48
○ 2026-07-24 05:51:00
○A3.33.251.1682026-04-06 → 2026-04-07 · 5 obs
● 2026-04-06 05:19:46
● 2026-04-07 05:23:40
○ 2026-04-08 22:41:42
○ 2026-07-24 05:51:00
○A34.111.179.2082026-03-29 → 2026-04-08 · 7 obs
● 2026-03-29 23:27:48
○ 2026-04-06 05:19:46
○ 2026-04-07 05:23:40
● 2026-04-08 22:41:42
○ 2026-05-23 20:49:32
○ 2026-07-24 05:51:00
○A50.63.202.882015-08-09 → 2017-02-07 · 4 obs
● 2017-02-07 21:52:48
○ 2018-07-29 01:03:40
○ 2026-07-24 05:51:00
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2018-07-29 → 2026-02-15 · 4 obs
● 2026-02-15 14:53:16
○ 2026-03-24 10:18:42
○ 2026-07-24 05:51:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net, a.gtld-servers.net... | - |
| whyrepipe.com | ns63.domaincontrol.com, ns64.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.69.42
NS records: ns63.domaincontrol.com, ns64.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for whyrepipe.com (unsigned zone)
⏱️ Timing
Total: 212ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 198.202.211.1 |
| NS | 3 | ns63.domaincontrol.com, ns64.domaincontrol.com... |
| MX | 1 | whyrepipe-com.mail.protection.outlook.co |
| TXT | 9 | google-site-verification=Z2RMGdXI6fD51ji, NETORGFT10627008.onmicrosoft.com... |
| SOA | 1 | ns63.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns63.domaincontrol.com, ns63.domaincontrol.com, ns64.domaincontrol.com...)
Analysis
Hierarchy
whyrepipe.com serves as the parent of epipe.whyrepipe.com and contact.whyrepipe.com.
IP Addresses
whyrepipe.com has exactly one IP address — 198.202.211.1.
wimmersolutions.com, cohesionib.com, bayerbuilt.com plus two other host names have IP numbers in common with whyrepipe.com.
Name Servers
DNS for whyrepipe.com is handled by three authoritative name servers: ns63.domaincontrol.com, ns64.domaincontrol.com and ernest.ns.cloudflare.com.
At least some of whyrepipe.com's name servers are shared with other domains, for example livecare.it, efxaudio.co, danegerous.me and two more.
These name servers tend to be used in conjunction with the name servers coco.ns.cloudflare.com.
Hosts with 6 IP addresses each:
ernest.ns.cloudflare.com has IP addresses 108.162.193.164, 172.64.33.164 and 173.245.59.164, plus 3 other.
Host names pointing to two IP addresses:
ns63.domaincontrol.com has two IP addresses: 97.74.101.42 and 2603:5:2154::2a.
ns64.domaincontrol.com has two IP addresses: 173.201.69.42 and 2603:5:2254::2a.
Mail Servers
whyrepipe.com uses one mail server — whyrepipe-com.mail.protection.outlook.com.
whyrepipe-com.mail.protection.outlook.com has 8 IP addresses: 52.101.9.0, 52.101.11.2, 52.101.40.1 plus 5 more.