proccident.com - dns.ninja
proccident.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=1783199481 | ||||||
Subdomains
mail.proccident.com |
Same first word
proccident.com |
Similar names
DNS History
9 records (8 active, 1 former)
●NSns1.mysecurecloudhost.com2026-04-10 → 2026-07-04 · 3 obs
● 2026-04-10 11:06:48
● 2026-07-04 21:24:04
●NSns2.mysecurecloudhost.com2026-04-10 → 2026-07-04 · 3 obs
● 2026-04-10 11:06:48
● 2026-07-04 21:24:04
●NSns3.mysecurecloudhost.com2026-04-10 → 2026-07-04 · 3 obs
● 2026-04-10 11:06:48
● 2026-07-04 21:24:04
●NSns3014.mochahost.com2019-12-15 → 2026-07-04 · 2 obs
● 2026-07-04 21:24:04
●NSns4.mysecurecloudhost.com2026-04-10 → 2026-07-04 · 3 obs
● 2026-04-10 11:06:48
● 2026-07-04 21:24:04
●NSns4014.mochahost.com2019-12-15 → 2026-07-04 · 2 obs
● 2026-07-04 21:24:04
●MXmail.proccident.com2019-12-15 → 2026-07-04 · 2 obs
● 2026-07-04 21:24:04
○A204.93.174.1362019-12-15 → 2019-12-15 · 3 obs
○ 2026-04-10 11:06:48
○ 2026-07-04 21:24:04
●A65.181.111.2372026-04-10 → 2026-07-04 · 3 obs
● 2026-04-10 11:06:48
● 2026-07-04 21:24:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, l.gtld-servers.net, h.gtld-servers.net, j.gtld-servers.net... | - |
| proccident.com | ns3014.mochahost.com, ns4014.mochahost.com | 2 records |
✅ Authoritative Response
Server:75.2.118.134
NS records: ns3014.mochahost.com, ns4014.mochahost.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for proccident.com (unsigned zone)
⏱️ Timing
Total: 223ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 65.181.111.237 |
| NS | 4 | ns2.mysecurecloudhost.com, ns1.mysecurecloudhost.com... |
| MX | 1 | mail.proccident.com (pri: 0) |
| TXT | 1 | v=spf1 ip4:65.181.111.237 include:spf.my |
| SOA | 1 | ns1.mysecurecloudhost.com servers.mysecu |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns3014.mochahost.com, ns4014.mochahost.com)
Analysis
Hierarchy
The domain mail.proccident.com falls under the parent proccident.com.
IP Addresses
proccident.com resolves to one IP address: 65.181.111.237.
autowims.com, tripkens.com, timex80.com and two other host names share IP numbers with proccident.com.
Name Servers
proccident.com carries NS records listing 6 name servers — ns3014.mochahost.com, ns4014.mochahost.com, ns1.mysecurecloudhost.com and 3 others.
At least some of proccident.com's name servers are shared with other domains, for example lanitaboyd.com, bitacoles.net, travelhoopers.com and two more.
It is common for these name servers to be used in conjunction with the name servers ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and ns4.mysecurecloudhost.com.
Hosts with just one IP address:
ns3014.mochahost.com resolves to the IP address 13.248.158.180.
ns4014.mochahost.com resolves to the IP address 75.2.118.134.
ns1.mysecurecloudhost.com resolves to the IP address 13.248.158.180.
ns2.mysecurecloudhost.com resolves to the IP address 75.2.118.134.
ns3.mysecurecloudhost.com resolves to the IP address 76.223.26.245.
ns4.mysecurecloudhost.com resolves to the IP address 99.83.147.209.
ns3014.mochahost.com and ns1.mysecurecloudhost.com each have 13.248.158.180 IP addresses.
ns4014.mochahost.com and ns2.mysecurecloudhost.com each have 75.2.118.134 IP addresses.
Mail Servers
Mail for proccident.com is handled by a single mail server, mail.proccident.com.
mail.proccident.com resolves to 65.181.111.237 and no other IP number.