Automated public DNS and web checks; results may be incomplete. These are passive observations, not an assessment of the organization.
Executive summary
code.berlin
High exposure. Significant weaknesses put the brand, customers and email at risk.
Full coverage: every applicable check was assessed.
2026-11-18 03:09 UTC
Useful for your IT provider or a colleague. Anyone with the link can view the report.
Track your progress
Fix the findings, then come back and rescan. Your scan history is saved in this browser so you can see exactly what improved.
Spoofing email from this domain is hard.
Traffic to the site is encrypted and the certificate is valid.
Several browser hardening headers are missing, which removes layers of protection against script injection and framing.
The domain's infrastructure works, but recommended hardening is missing.
Help someone else check their domain
Share this public report with a colleague. They can review the evidence and check their own domain.
What to do first
- 1.
Tell browsers to always use the secure version
Helps browsers use HTTPS on future visits after they have received the policy.
Who can fix it: Your web host
How to verify after the fix
curl -sIL https://code.berlin/ | grep -i "Strict-Transport-Security"
- 2.
Limit what scripts your pages are allowed to run
This adds one layer of protection against injected scripts.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://code.berlin/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- code.berlin
- Website request
- GET https://code.berlin/
- Scan time
- 2026-11-18 03:09:02 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Show the live grade for code.berlin in a README, docs or site footer. The badge links to the public report and refreshes every 24 hours.
Scan shown on this page: 2026-11-18 03:09:02 UTC. The badge may display a cached result for up to 24 hours. Open the linked report to check its scan time.
[](https://getmirror.online/report/code.berlin)<a href="https://getmirror.online/report/code.berlin"><img src="https://getmirror.online/badge/code.berlin.svg" alt="Domain Armor grade"></a>https://getmirror.online/badge/code.berlin.svgScan history
AI fix plan
Pick scans from this browser's history. The AI compares them, explains what changed and builds a prioritized, step-by-step plan.
Scans to analyze
0 of 6 selectedThe current scan is always included.
AI-generated from your scan results only. Review each step before applying it; nothing is sent to or changed on the domain.
Technical detail
Click a check to see the public data, a verification command, a safe fix recommendation and documentation sources.
Email security
27/30Encryption & certificate
25/25Browser protections
0/30DNS infrastructure
8/15Public DNS records
| A | code.berlin | 3.174.2.62 3.174.2.86 3.174.2.47 3.174.2.88 |
| AAAA | code.berlin | — |
| MX | code.berlin | 1 aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com |
| NS | code.berlin | ns-1333.awsdns-38.org ns-1668.awsdns-16.co.uk ns-265.awsdns-33.com ns-625.awsdns-14.net |
| TXT | code.berlin | MS=A6B98215BED0CE2C89C29A5DBB37CE94DA6D5CEF MS=ms31871371 ZOOM_verify_buC0GCbU3MnY1TW96qNJF8 atlassian-domain-verification=MweL1DVhtXwzJsQxCy86SVpRh169ZJOddz6APfiOHyjZzmYZIqF5ro3Le7KaWSw1 atlassian-sending-domain-verification=83abf972-1013-49ab-94a1-4473f37dfcdf brevo-code:0c5fa1670226f361ddf5700f066c93fe google-site-verification=15HVflHO-1vO-qwdOHcIFhD3WAcbOtlQVUW4wom2efg google-site-verification=93pfToGJCcawdDxgEbRc_ZUKyeMM4313c_uYiCHSaVY google-site-verification=Pom-mwhb8KaxeJN1KEODs8OpOtvpoJ1cARfmOby5DRQ google-site-verification=W8Oe95DyB8rE4Nn_2VMJc3XnUIroeCk26E-7bXS3RXw google-site-verification=ezyuzxQxaS97B2w5x893sbpD0Hd0_1zaI7IsPIQHm24 google-site-verification=sOPgLz3uOroQh6D75LqXHg4TyXUIfKrEUzB-7GDpqe8 jamf-site-verification=U4QosJ6v4z5NNxmOqoxcvg miro-verification=87dd53c91e616679d0c0074c2099ac8649461d47 notion_verify_fG*G%.A05D,aW%uYF>ZM>YJ_p>m!Kj]yQ0y_fm4yQ#Kg1mhg4.QWi~UauWX>_6~qsxtXve v=spf1 include:_spf.google.com include:2730872.spf04.hubspotemail.net include:_spf.atlassian.net ~all |
| TXT | _dmarc.code.berlin | v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@code.berlin |
| CAA | code.berlin | 0 issue "awstrust.com" 0 issue "digicert.com" 0 issue "letsencrypt.org" |
| DS | code.berlin | — |