peppymode.com - dns.ninja
peppymode.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=1783857062 | ||||||
Same first word
peppymode.com |
DNS History
10 records (6 active, 4 former)
●NSns35.domaincontrol.com2018-11-18 → 2026-07-12 · 2 obs
● 2026-07-12 12:11:26
●NSns36.domaincontrol.com2018-11-18 → 2026-07-12 · 2 obs
● 2026-07-12 12:11:26
●A156.67.220.862020-10-10 → 2026-07-12 · 3 obs
● 2020-10-10 10:15:52
● 2026-07-12 12:11:26
○A160.153.136.32018-11-18 → 2018-11-18 · 3 obs
○ 2020-10-10 10:15:52
○ 2026-07-12 12:11:26
○A182.50.132.2422018-11-18 → 2018-11-18 · 3 obs
○ 2026-03-07 21:42:28
○ 2026-07-12 12:11:26
○A198.71.232.32018-11-18 → 2018-11-18 · 3 obs
○ 2026-03-07 21:42:28
○ 2026-07-12 12:11:26
○A72.167.191.692018-11-18 → 2018-11-18 · 3 obs
○ 2026-03-07 21:42:28
○ 2026-07-12 12:11:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, j.gtld-servers.net, f.gtld-servers.net, d.gtld-servers.net... | - |
| peppymode.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 peppymode.com (unsigned zone)
⏱️ Timing
Total: 146ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 156.67.220.86 |
| NS | 2 | ns35.domaincontrol.com, ns36.domaincontrol.com |
| MX | 3 | mx2.zoho.in (pri: 20), mx3.zoho.in (pri: 50)... |
| TXT | 3 | v=spf1 include:zoho.in ~all, v=spf1 include:mailgun.org ~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
peppymode.com resolves to just one IP address, 156.67.220.86.
There are other host names — srv538825.hstgr.cloud among them — that share IP numbers with peppymode.com.
Name Servers
DNS delegation for peppymode.com points to two name servers: ns35.domaincontrol.com and ns36.domaincontrol.com.
peppymode.com shares its NS records with other domains, for example antifreak.com, aldineaft.org, connectionupdate.com and two others.
ns35.domaincontrol.com directs to 97.74.107.18 and 2603:5:21b1::12. ns36.domaincontrol.com directs to 173.201.75.18 and 2603:5:22b1::12. Each host name carries two IP addresses.
Mail Servers
Incoming mail for peppymode.com is delivered via three mail servers: mx2.zoho.in, mx3.zoho.in and mx.zoho.in.
There is at least a partial MX overlap between peppymode.com and other domains, including profindo.com.sg, globalskycargo.com, thelucknowpost.com and two others.
Host names that have two IP addresses:
mx2.zoho.in has two IP addresses: 169.148.146.168 and 169.148.149.118.
mx.zoho.in has two IP addresses: 169.148.146.168 and 169.148.149.118.
Host names that point to one IP address:
mx3.zoho.in directs to 103.103.196.235.
Host names pointing to 169.148.146.168 IP addresses: mx2.zoho.in and mx.zoho.in.
Host names pointing to 169.148.149.118 IP addresses: mx2.zoho.in and mx.zoho.in.