Identity
69
C
thenextweb.com
Posture Score: 79/100
Scanned May 30, 2026 at 11:15 AM UTC
Attack Surface
77
Reputation
91
Identity Findings
Subdomains have no DMARC enforcement
No sp= tag set and p=none. Subdomains inherit the monitoring-only policy, leaving them open to spoofing.
💡 Add sp=reject (or sp=quarantine) to your DMARC record to protect subdomains.
MX hostname does not resolve: taylor.mxrouting.net.thenextweb.com
The MX hostname has no A or AAAA records.
💡 Ensure the MX hostname resolves to a valid IP address.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.thenextweb.com
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
ManageSieve port 4190 open on taylor.mxrouting.net
Port 4190 (ManageSieve) is publicly accessible. This should typically be restricted.
💡 Restrict port 4190 access to authorized networks via firewall rules.
MTA-STS is in testing mode
The MTA-STS policy is in testing mode and not actively enforcing TLS.
💡 Switch mode to "enforce" once TLS is confirmed working for all MX hosts.
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
No CAA iodef tag configured
No iodef tag is present in the CAA records. CA policy violation reports will not be sent.
💡 Add an iodef CAA record. Example: 0 iodef "mailto:security@example.com"
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (31 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
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.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
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.
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
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.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on taylor.mxrouting.net
Detected open mail-related ports: 25, 110, 143, 465, 587, 993, 995, 4190
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2405459833, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Authorized certificate authorities
CAA records restrict certificate issuance to: certainly.com, pki.goog; cansignhttpexchanges=yes, ssl.com, amazontrust.com, comodoca.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org, amazon.com
Attack Surface Findings
Dangling MX: taylor.mxrouting.net.thenextweb.com does not resolve
The MX record points to taylor.mxrouting.net.thenextweb.com which has no A record. This may indicate a decommissioned mail provider (Unknown). Attackers can potentially re-register this hostname to hijack inbound mail.
💡 Remove the stale MX record pointing to taylor.mxrouting.net.thenextweb.com or update it to your current mail provider.
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.
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.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
5 subdomain(s) discovered for thenextweb.com
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 thenextweb.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain thenextweb.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled but missing preload directive on thenextweb.com
Strict-Transport-Security: max-age=2592000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://thenextweb.com/.well-known/security.txt.
TLS certificate valid for 33 days
Certificate for thenextweb.com expires on 2026-07-02.
Certificate issued by E8
The certificate for thenextweb.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for thenextweb.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for thenextweb.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for thenextweb.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on thenextweb.com.
Domain valid for 1890 days
Domain thenextweb.com expires on 2031-08-02.
No disposable email provider MX records
MX records for thenextweb.com do not match known disposable email provider patterns.
Domain is 6509 days old
Domain thenextweb.com was registered 2008-08-02.
No wildcard MX records
No wildcard MX records detected for thenextweb.com.
TLD has good reputation
The .com 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 (taylor.mxrouting.net) 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.
Could not connect to webmail.thenextweb.com
HTTPS request to https://webmail.thenextweb.com failed or timed out.
WHOIS registration data
Registrar: NameCheap, Inc. | Created: 2008-08-02 | Expires: 2031-08-02 | Updated: 2026-04-03
WHOIS privacy protection enabled
Domain thenextweb.com has WHOIS privacy/redaction enabled.
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: thenetweb.com (has MX!), thenexweb.com (has MX!), thenextwe.com (has MX!), henextweb.com
4 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: none
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: none
Mail Server Identity: taylor.mxrouting.net
PTR record proves mail server legitimacy
MX: taylor.mxrouting.net
Mail server at 168.119.13.219
→
PTR Record
Reverse DNS: taylor.mxrouting.net
Mail Server Identity: taylor.mxrouting.net.thenextweb.com
PTR record proves mail server legitimacy
MX: taylor.mxrouting.net.thenextweb.com
Mail server at taylor.mxrouting.net.thenextweb.com
→
PTR Record
No PTR record
⚠️ Mail server taylor.mxrouting.net.thenextweb.com (taylor.mxrouting.net.thenextweb.com) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: taylor.mxrouting.net
RBL check ensures server is not blacklisted
MX: taylor.mxrouting.net
Mail server at 168.119.13.219
→
RBL Status
Not blacklisted
Mail Server Reputation: taylor.mxrouting.net.thenextweb.com
RBL check ensures server is not blacklisted
MX: taylor.mxrouting.net.thenextweb.com
Mail server at taylor.mxrouting.net.thenextweb.com
→
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: testing
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
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/thenextweb.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan thenextweb.com Again