← Back to Scanner
C

deviantart.com

Posture Score: 73/100

Scanned May 27, 2026 at 1:10 PM UTC

Identity

40

Attack Surface

87

Reputation

92

Identity Findings

No NS records found
No nameserver records could be retrieved for this domain.
💡 Ensure NS records are properly configured at your registrar and in your zone file.
critical
External report destination not authorized: wix.com
The rua= URI sends reports to wix.com, but no authorization record exists at deviantart.com._report._dmarc.wix.com. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of wix.com to publish a TXT record at deviantart.com._report._dmarc.wix.com containing 'v=DMARC1'.
high
External report destination not authorized: wix.com
The rua= URI sends reports to wix.com, but no authorization record exists at deviantart.com._report._dmarc.wix.com. Reports will be silently dropped by compliant receivers.
💡 Ask the owner of wix.com to publish a TXT record at deviantart.com._report._dmarc.wix.com containing 'v=DMARC1'.
high
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
high
External DMARC report destination not authorized: wix.com
The rua= URI points to wix.com but no authorization record exists at deviantart.com._report._dmarc.wix.com.
💡 Ask the owner of wix.com to publish a TXT record at deviantart.com._report._dmarc.wix.com with 'v=DMARC1'.
medium
External DMARC report destination not authorized: wix.com
The rua= URI points to wix.com but no authorization record exists at deviantart.com._report._dmarc.wix.com.
💡 Ask the owner of wix.com to publish a TXT record at deviantart.com._report._dmarc.wix.com with 'v=DMARC1'.
medium
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.deviantart.com/.well-known/mta-sts.txt
medium
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
medium
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"
medium
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@deviantart.com").
low
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
pass
SPF record length OK (35 bytes)
SPF record is within safe DNS packet size limits.
pass
DKIM records are valid
DKIM records found and validated for selectors: google
pass
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
pass
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
pass
Subdomains protected (sp=quarantine)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
pass
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
pass
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
pass
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
pass
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
pass
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
pass
IPv6 readiness is good
IPv6 records are present and properly configured.
pass
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
pass
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.
informational
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
informational
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.
informational
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.
informational
Shared/free email hosting detected: aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
informational
Shared/free email hosting detected: alt3.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
informational
Shared/free email hosting detected: alt4.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
informational
Shared/free email hosting detected: alt1.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
informational
Shared/free email hosting detected: alt2.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
informational
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.
informational
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
informational
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
informational
Open mail ports on aspmx.l.google.com
Detected open mail-related ports: 25
informational
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.
informational
MX IP network diversity
MX IPs span 5 different /16 networks, providing good diversity.
informational
SOA record parameters
Serial: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s
informational

Attack Surface Findings

Non-routable IPv4 in public DNS: ftp.deviantart.com → 127.0.0.1
The subdomain ftp.deviantart.com resolves to non-routable IP 127.0.0.1, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
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.
medium
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
low
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
pass
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
pass
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
pass
6 subdomain(s) discovered for deviantart.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
informational
84 certificate(s) found in CT logs
Certificate Transparency logs contain 84 certificate(s) for deviantart.com and its subdomains. Each certificate reveals subdomain names.
informational
Wildcard DNS record detected
A wildcard DNS record exists for *.deviantart.com, resolving to 54.230.114.125, 54.230.114.38, 54.230.114.76, 54.230.114.92. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
informational
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.deviantart.com is active and requires authentication.
informational

Reputation Findings

Missing Strict-Transport-Security on deviantart.com
The Strict-Transport-Security header is not set on https://deviantart.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
medium
Missing Strict-Transport-Security on webmail.deviantart.com
The Strict-Transport-Security header is not set on https://webmail.deviantart.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
medium
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
pass
security.txt present
Found security.txt at https://deviantart.com/.well-known/security.txt.
pass
TLS certificate valid for 87 days
Certificate for deviantart.com expires on 2026-08-22.
pass
Certificate issued by Amazon RSA 2048 M02
The certificate for deviantart.com is issued by a third-party CA.
pass
Signature algorithm: rsa-sha256
The certificate for deviantart.com uses an acceptable signature algorithm.
pass
RSA key: 2048 bits
The certificate for deviantart.com uses an adequate RSA key of 2048 bits.
pass
SCTs present in certificate
The certificate for deviantart.com contains Signed Certificate Timestamps.
pass
No weak ciphers detected
No known weak cipher suites detected on deviantart.com.
pass
Domain valid for 2264 days
Domain deviantart.com expires on 2032-08-08.
pass
Domain transfer and delete locks enabled
Domain deviantart.com has clientTransferProhibited and clientDeleteProhibited locks.
pass
No disposable email provider MX records
MX records for deviantart.com do not match known disposable email provider patterns.
pass
Domain is 9528 days old
Domain deviantart.com was registered 2000-04-25.
pass
No wildcard MX records
No wildcard MX records detected for deviantart.com.
pass
TLD has good reputation
The .com TLD is not on known abuse watchlists.
pass
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
pass
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
pass
Strong TLS configuration on primary MX
Primary MX (aspmx.l.google.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
pass
SMTP banner from hosted mail provider
The MX (aspmx.l.google.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
pass
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.
informational
Abuse contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
informational
PhishTank — API key required
PhishTank phishing database check requires an API key.
informational
Sender Score — API key required
Sender Score reputation check requires an API key.
informational
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
informational
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 2000-04-25 | Expires: 2032-08-08 | Updated: 2023-04-17
informational
WHOIS privacy protection enabled
Domain deviantart.com has WHOIS privacy/redaction enabled.
informational
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
informational
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
informational
Typosquat detected: eviantart.com (has MX!), dviantart.com (has MX!), deiantart.com (has MX!), devintart.com (has MX!), deviatart.com (has MX!)
22 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 22. Domains with MX records can send and receive email, making them high-risk phishing vectors.
informational

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.
Mail Server Identity: aspmx.l.google.com
PTR record proves mail server legitimacy
MX: aspmx.l.google.com Mail server at 209.85.202.26 → PTR Record Reverse DNS: dg-in-f26.1e100.net
Mail Server Identity: alt3.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt3.aspmx.l.google.com Mail server at 192.178.213.26 → PTR Record Reverse DNS: yugrqzs-in-f26.1e100.net
Mail Server Identity: alt4.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt4.aspmx.l.google.com Mail server at 142.251.127.26 → PTR Record Reverse DNS: lcfrai-in-f26.1e100.net
Mail Server Identity: alt1.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt1.aspmx.l.google.com Mail server at 173.194.76.26 → PTR Record Reverse DNS: ws-in-f26.1e100.net
Mail Server Identity: alt2.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt2.aspmx.l.google.com Mail server at 142.250.102.27 → PTR Record Reverse DNS: rb-in-f27.1e100.net
Mail Server Reputation: aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: aspmx.l.google.com Mail server at 209.85.202.26 → RBL Status Not blacklisted
Mail Server Reputation: alt3.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt3.aspmx.l.google.com Mail server at 192.178.213.26 → RBL Status Not blacklisted
Mail Server Reputation: alt4.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt4.aspmx.l.google.com Mail server at 142.251.127.26 → RBL Status Not blacklisted
Mail Server Reputation: alt1.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt1.aspmx.l.google.com Mail server at 173.194.76.26 → RBL Status Not blacklisted
Mail Server Reputation: alt2.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt2.aspmx.l.google.com Mail server at 142.250.102.27 → 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 MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement DMARC policy: quarantine → BIMI Record BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support Mail servers support TLS encryption → TLS-RPT Reporting TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.

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:

deviantart.com Email Security Grade
<img src="https://scan.ractermx.com/badge/deviantart.com.svg" alt="Email Security Grade">

Want to re-scan this domain for updated results?

Scan deviantart.com Again