developerhouse.com - dns.ninja
developerhouse.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=1782639705 | ||||||
MX for
developerhouse.com |
Subdomains
www.developerhouse.com |
Same first word
developerhouse.com |
Similar names
DNS History
8 records (5 active, 3 former)
βNSns1.md-in-19.webhostbox.net2015-08-19 β 2017-04-08 Β· 4 obs
β 2017-04-08 13:56:16
β 2026-03-14 10:52:58
β 2026-06-28 09:42:28
βNSns2.md-in-19.webhostbox.net2015-08-19 β 2017-04-08 Β· 4 obs
β 2017-04-08 13:56:16
β 2026-03-14 10:52:58
β 2026-06-28 09:42:28
βNSns45.domaincontrol.com2026-03-14 β 2026-06-28 Β· 3 obs
β 2026-03-14 10:52:58
β 2026-06-28 09:42:28
βNSns46.domaincontrol.com2026-03-14 β 2026-06-28 Β· 3 obs
β 2026-03-14 10:52:58
β 2026-06-28 09:42:28
βMXdeveloperhouse.com2015-08-19 β 2026-06-28 Β· 2 obs
β 2026-06-28 09:42:28
βMXinbound-smtp.us-east-1.amazonaws.com2026-03-14 β 2026-06-28 Β· 3 obs
β 2026-03-14 10:52:58
β 2026-06-28 09:42:28
βA3.80.98.42026-03-14 β 2026-06-28 Β· 3 obs
β 2026-03-14 10:52:58
β 2026-06-28 09:42:28
βA43.225.55.2402015-08-19 β 2017-04-08 Β· 4 obs
β 2017-04-08 13:56:16
β 2026-03-14 10:52:58
β 2026-06-28 09:42:28
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, g.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net... | - |
| developerhouse.com | ns45.domaincontrol.com, ns46.domaincontrol.com | 4 records |
β Authoritative Response
Server:97.74.102.23
NS records: ns45.domaincontrol.com, ns46.domaincontrol.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for developerhouse.com (unsigned zone)
β±οΈ Timing
Total: 192ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 3.80.98.4 |
| NS | 2 | ns45.domaincontrol.com, ns46.domaincontrol.com |
| MX | 2 | inbound-smtp.us-east-1.amazonaws.com (pr, developerhouse.com (pri: 1) |
| TXT | 2 | v=spf1 include:amazonses.com ~all, ahrefs-site-verification_088992fcc5c11a1 |
| SOA | 1 | ns45.domaincontrol.com dns.jomax.net |
π Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns45.domaincontrol.com, ns45.domaincontrol.com, ns46.domaincontrol.com...)
Analysis
Hierarchy
developerhouse.com serves as the parent of www.developerhouse.com.
Mail Server Role
developerhouse.com serves as a mail server for developerhouse.com.
As mail servers, inbound-smtp.us-east-1.amazonaws.com and developerhouse.com are regularly found together.
IP Addresses
developerhouse.com has exactly one IP address β 3.80.98.4.
Name Servers
developerhouse.com uses two name servers for its delegation: ns45.domaincontrol.com and ns46.domaincontrol.com.
The name server configuration of developerhouse.com is shared with other domains, for instance rotemberger.com, causalintelligence.net, tcb-landscape.com and two others.
The two host names ns45.domaincontrol.com and ns46.domaincontrol.com each have a pair of IP addresses: ns45.domaincontrol.com has 97.74.102.23 and 2603:5:2162::17, and ns46.domaincontrol.com has 173.201.70.23 and 2603:5:2262::17.
Mail Servers
The domain developerhouse.com has two mail servers: developerhouse.com and inbound-smtp.us-east-1.amazonaws.com.
At least some of the mail servers used by developerhouse.com are shared with other domains: localizely.com, heli-chair.com, mibexsoftware.atlassian.net and two others among them.
These mail servers tend to be used in conjunction with the mail servers inbound-smtp.us-west-2.amazonaws.com.
Hosts with five IP addresses:
inbound-smtp.us-east-1.amazonaws.com has IP addresses 3.211.210.226, 44.206.9.87 and 44.210.166.32 along with two other addresses.
Host names resolving to a single IP address: