Identity
99
A
mailsec.se
Posture Score: 90/100
Scanned July 2, 2026 at 3:15 PM UTC
Attack Surface
80
Reputation
92
Identity Findings
Shared IP 64.112.125.37 used by multiple MX servers
The IP 64.112.125.37 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (36 bytes)
SPF record is within safe DNS packet size limits.
DKIM records are valid
DKIM records found and validated for selectors: dkim
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
MX records are valid
All MX records are properly configured.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=s, aspf=s
DKIM alignment is strict, SPF alignment is strict.
DMARC failure reporting: fo=1:d:s
Failure reporting option: 1:d:s
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
DANE/TLSA configured for mail.mailsec.se
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for mx.mailsec.se
TLSA records found and TLS certificate is available for verification.
No VMC authority URL in BIMI record
The BIMI record does not specify a VMC (a= tag). Gmail and Apple Mail require a VMC to display brand logos.
Open mail ports on mail.mailsec.se
Detected open mail-related ports: 25, 587, 993
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2408437014, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Authorized certificate authorities
CAA records restrict certificate issuance to: pki.goog; cansignhttpexchanges=yes, ssl.com, comodoca.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org
TLSA record TTL: 300s
The TLSA record has a TTL of 300s. Ensure this is shorter than half the certificate validity period.
TLSA record TTL: 300s
The TLSA record has a TTL of 300s. Ensure this is shorter than half the certificate validity period.
Attack Surface Findings
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
Microsoft Autodiscover accessible without authentication
The Autodiscover endpoint at https://autodiscover.mailsec.se/autodiscover/autodiscover.xml returns configuration data without requiring authentication. This exposes email server details to unauthenticated users.
💡 Configure the Autodiscover endpoint to require authentication before returning configuration data.
No NSEC/NSEC3 records found
Neither NSEC nor NSEC3 records were found. Authenticated denial of existence is not configured.
💡 Configure NSEC3 records for authenticated denial of existence while preventing zone enumeration.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
2 subdomain(s) discovered for mailsec.se
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for mailsec.se and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.mailsec.se, resolving to 64.112.125.37. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.mailsec.se is publicly accessible.
1 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Missing domain locks: clientTransferProhibited, clientDeleteProhibited
Domain mailsec.se is missing protective locks: clientTransferProhibited, clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on mailsec.se
Strict-Transport-Security: max-age=47474747; includeSubDomains; preload
HSTS enabled with preload on webmail.mailsec.se
Strict-Transport-Security: max-age=47474747; includeSubDomains; preload
security.txt present
Found security.txt at https://mailsec.se/.well-known/security.txt.
TLS certificate valid for 89 days
Certificate for mailsec.se expires on 2026-09-29.
Certificate issued by YE1
The certificate for mailsec.se is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for mailsec.se uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for mailsec.se uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for mailsec.se contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on mailsec.se.
Domain valid for 169 days
Domain mailsec.se expires on 2026-12-19.
No disposable email provider MX records
MX records for mailsec.se do not match known disposable email provider patterns.
Domain is 926 days old
Domain mailsec.se was registered 2023-12-19.
No wildcard MX records
No wildcard MX records detected for mailsec.se.
TLD has good reputation
The .se TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mail.mailsec.se) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
WHOIS registration data
Registrar: Hostup AB | Created: 2023-12-19 | Expires: 2026-12-19 | Updated: Unknown
WHOIS privacy protection not detected
Domain mailsec.se does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: milsec.se (has MX!)
1 registered lookalike domain(s) that could be used for phishing against your brand. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: reject
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature configured
→
DMARC Policy
DMARC policy: reject
Mail Server Identity: mail.mailsec.se
PTR record proves mail server legitimacy
MX: mail.mailsec.se
Mail server at 64.112.125.37
→
PTR Record
Reverse DNS: mail.mailsec.se
Mail Server Identity: mx.mailsec.se
PTR record proves mail server legitimacy
MX: mx.mailsec.se
Mail server at 64.112.125.37
→
PTR Record
Reverse DNS: mail.mailsec.se
Mail Server Reputation: mail.mailsec.se
RBL check ensures server is not blacklisted
MX: mail.mailsec.se
Mail server at 64.112.125.37
→
RBL Status
Not blacklisted
Mail Server Reputation: mx.mailsec.se
RBL check ensures server is not blacklisted
MX: mx.mailsec.se
Mail server at 64.112.125.37
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
Mode: enforce
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
Brand logo configured
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS failure reporting configured
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✓
DMARC Policy
✓
BIMI Record
✓
CAA Records
✓
DNSSEC
✓
MTA-STS
✓
TLS-RPT
✓
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/mailsec.se.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan mailsec.se Again