developersbreach.com - dns.ninja
developersbreach.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=1782692500 | ||||||
Same first word
developersbreach.com |
DNS History
12 records (10 active, 2 former)
●NSns1.wordpress.com2018-08-31 → 2026-06-29 · 2 obs
● 2026-06-29 00:24:02
●NSns2.wordpress.com2018-08-31 → 2026-06-29 · 2 obs
● 2026-06-29 00:24:02
●NSns3.wordpress.com2018-08-31 → 2026-06-29 · 2 obs
● 2026-06-29 00:24:02
●MXalt1.aspmx.l.google.com2026-06-29 → 2026-06-29 · 2 obs
● 2026-06-29 00:24:02
●MXalt2.aspmx.l.google.com2026-06-29 → 2026-06-29 · 2 obs
● 2026-06-29 00:24:02
●MXalt3.aspmx.l.google.com2026-06-29 → 2026-06-29 · 2 obs
● 2026-06-29 00:24:02
●MXalt4.aspmx.l.google.com2026-06-29 → 2026-06-29 · 2 obs
● 2026-06-29 00:24:02
●MXaspmx.l.google.com2026-06-29 → 2026-06-29 · 2 obs
● 2026-06-29 00:24:02
●A192.0.78.1352026-06-29 → 2026-06-29 · 3 obs
● 2026-06-29 00:23:58
● 2026-06-29 00:24:02
●A192.0.78.1942026-06-29 → 2026-06-29 · 3 obs
● 2026-06-29 00:23:58
● 2026-06-29 00:24:02
○A192.0.78.242018-08-31 → 2018-08-31 · 3 obs
○ 2026-06-29 00:23:58
○ 2026-06-29 00:24:02
○A192.0.78.252018-08-31 → 2018-08-31 · 3 obs
○ 2026-06-29 00:23:58
○ 2026-06-29 00:24:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| developersbreach.com | ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com | 6 records |
✅ Authoritative Response
Server:198.181.116.9
NS records: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for developersbreach.com (unsigned zone)
⏱️ Timing
Total: 161ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 192.0.78.135, 192.0.78.194 |
| NS | 3 | ns1.wordpress.com, ns3.wordpress.com... |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 include:_spf.wpcloud.com include:, google-site-verification=dCUbstcVbekV7-I |
| SOA | 1 | ns1.wordpress.com hostmaster.wordpress.c |
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns1.wordpress.com, ns1.wordpress.com, ns2.wordpress.com...)
Analysis
IP Addresses
developersbreach.com points to the IP addresses 192.0.78.135 and 192.0.78.194
Two other host names, along with rakisproductions.com, ateliedeeventos.com.br and tsc.net.sa, also share IP numbers with developersbreach.com.
Name Servers
developersbreach.com carries NS records delegating to ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com.
There is at least partial name server overlap between developersbreach.com and other domains — psychicfortunes.com, shadetreepro.com, aakrutikannada.com and two more among them.
ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com are three hostnames that each resolve to a pair of IP addresses: ns1.wordpress.com to 198.181.116.9 and 2a04:fa87:ffff::c6b5:7409, ns2.wordpress.com to 198.181.117.9 and 2a04:fa87:ffff::c6b5:7509, and ns3.wordpress.com to 192.0.74.9 and 2620:115:c00f::c000:4a09.
Mail Servers
developersbreach.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between developersbreach.com and other domains, including ns500699.ns500734.ns500699.ns500734.ns500693.ns500693.ns500693.ns500734.ns500699.ns500612.ns500612.ns500612.ns500612.ns500612.ns500110.dtrkdll.com, ns500754.ns500671.ns500754.ns500671.ns500731.ns500688.ns500704.ns500704.ns500671.ns500649.ns500649.ns500291.ns500131.lustychickser.com, ns500754.ns500742.ns500731.ns500754.ns500678.ns500704.ns500671.ns500649.ns500649.ns500291.ns500131.lustychickser.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com resolves to two addresses: 142.251.16.27 and 2607:f8b0:4004:c1f::1b.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1a.