dashburst.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

29risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

0Medium

2Low

2Info

Collected 9 hours ago68.1sfrom cache

Headers—

unavailable

noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
noteSecurity headers did not complete (20). Results below are partial.

SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.dashburst.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@dashburst.com"`, review the reports, then move to p=quarantine and p=reject.
asset: dashburst.com
dev.dashburst.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev.dashburst.com
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: dashburst.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: dashburst.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: dashburst.com

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
!SPFends in ~all
v=spf1 include:_spf.google.com ip4:dashburst.com include:spf.mandrillapp.com ~all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-11.awsdns-01.com ns-1474.awsdns-56.org ns-1721.awsdns-23.co.uk ns-782.awsdns-33.net

✓Registered with GoDaddy.com, LLC15.7 years old
dashburst.com
✓Registration expiry115 days
2026-12-31
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓4 nameservers at registry
ns-11.awsdns-01.com ns-1474.awsdns-56.org ns-1721.awsdns-23.co.uk ns-782.awsdns-33.net

Address	Ports	Edge	Network
52.54.115.148 blog.dashburst.com +4	80443	direct	—
74.114.154.22 links.dashburst.com +2	80443	direct	—
74.114.154.18 links.dashburst.com +2	80443	direct	—
18.211.134.104 dashburst.com +1	none known	direct	—
192.241.243.183 dev.dashburst.com +1	none known	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.