Identity
63
D
notion.so
Posture Score: 66/100
Scanned May 8, 2026 at 7:36 AM UTC
Attack Surface
44
Reputation
92
Identity Findings
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.notion.so
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.notion.so/.well-known/mta-sts.txt
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@notion.so").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
Very low TTL on TXT records: 297s
7 TXT records have a TTL of 297s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 297s
The SPF record has a TTL of 297s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 297s
The DMARC record has a TTL of 297s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7197s) differs significantly from the authoritative zone (~86400s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
IPv6 readiness is good
IPv6 records are present and properly configured.
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=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
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.
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
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.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
Open relay check skipped — no MX records
Cannot test for open relay without MX records.
SMTP compliance check skipped — no MX records
Cannot test SMTP compliance without MX records.
Port exposure check skipped — no MX records
Cannot scan ports without MX records.
STARTTLS downgrade check skipped — no MX records
Cannot test STARTTLS without MX records.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 2402988275, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Non-routable IPv4 in public DNS: admin.notion.so → 10.96.163.153
The subdomain admin.notion.so resolves to non-routable IP 10.96.163.153, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: admin.notion.so → 10.96.14.208
The subdomain admin.notion.so resolves to non-routable IP 10.96.14.208, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: admin.notion.so → 10.96.127.148
The subdomain admin.notion.so resolves to non-routable IP 10.96.127.148, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-responsive IP for www.notion.so: 2602:f79a::2
The subdomain www.notion.so resolves to 2602:f79a::2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2602:f79a::2 is operational or remove the DNS record for www.notion.so.
Non-responsive IP for www.notion.so: 2602:f79a::1
The subdomain www.notion.so resolves to 2602:f79a::1 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2602:f79a::1 is operational or remove the DNS record for www.notion.so.
Non-responsive IP for dev.notion.so: 2602:f79a::1
The subdomain dev.notion.so resolves to 2602:f79a::1 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2602:f79a::1 is operational or remove the DNS record for dev.notion.so.
Non-responsive IP for dev.notion.so: 2602:f79a::2
The subdomain dev.notion.so resolves to 2602:f79a::2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2602:f79a::2 is operational or remove the DNS record for dev.notion.so.
Non-responsive IP for status.notion.so: 2602:f79a::2
The subdomain status.notion.so resolves to 2602:f79a::2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2602:f79a::2 is operational or remove the DNS record for status.notion.so.
Non-responsive IP for status.notion.so: 2602:f79a::1
The subdomain status.notion.so resolves to 2602:f79a::1 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2602:f79a::1 is operational or remove the DNS record for status.notion.so.
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
5 subdomain(s) discovered for notion.so
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 notion.so and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain notion.so is missing protective locks: 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 notion.so
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://notion.so/.well-known/security.txt.
TLS certificate valid for 69 days
Certificate for notion.so expires on 2026-07-16.
Certificate issued by WE1
The certificate for notion.so is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for notion.so uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for notion.so uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for notion.so contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on notion.so.
Domain valid for 326 days
Domain notion.so expires on 2027-03-31.
No disposable email provider MX records
MX records for notion.so do not match known disposable email provider patterns.
Domain is 4056 days old
Domain notion.so was registered 2015-03-31.
No wildcard MX records
No wildcard MX records detected for notion.so.
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.
No abuse contacts resolved
Could not resolve abuse contact information for MX IPs via abusix.org.
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.
Could not connect to webmail.notion.so
HTTPS request to https://webmail.notion.so failed or timed out.
WHOIS registration data
Registrar: 1API | Created: 2015-03-31 | Expires: 2027-03-31 | Updated: 2026-04-24
WHOIS privacy protection not detected
Domain notion.so 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).
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: quarantine
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature missing
→
DMARC Policy
DMARC policy: quarantine
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: quarantine
→
BIMI Record
Brand logo configured
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/notion.so.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan notion.so Again