paywb.com

Name: paywb.com Email Security Posture Assessment
Creator: RacterMX
License: https://creativecommons.org/licenses/by-nc/4.0/

Posture Score: 56/100

Scanned May 29, 2026 at 3:36 PM UTC

Score History

Identity

Attack Surface

Reputation

Identity Findings

Multiple SPF records detected

Multiple SPF records cause undefined behavior per RFC 7208. Only one SPF record should exist.

💡 Merge all SPF records into a single TXT record.

critical

No DMARC record found

The domain has no DMARC record, providing no policy for handling unauthenticated email.

💡 Publish a DMARC TXT record at _dmarc.paywb.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@paywb.com").

critical

Does not meet bulk sender requirements

Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: No DMARC record published (required since Feb 2024)

💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.

high

FCrDNS failure: no PTR for 91.230.107.131 (mail01.corp.wildberries.ru)

The IP 91.230.107.131 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.

💡 Configure a PTR record for the IP that matches the mail server hostname.

high

FCrDNS mismatch: 91.230.107.133 → collectorbsd.wildberries.ru does not resolve back

PTR for 91.230.107.133 is collectorbsd.wildberries.ru, but collectorbsd.wildberries.ru does not resolve back to 91.230.107.133.

💡 Ensure the PTR hostname resolves back to the original IP address.

high

FCrDNS failure: no PTR for 91.230.107.132 (mail02.corp.wildberries.ru)

The IP 91.230.107.132 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.

💡 Configure a PTR record for the IP that matches the mail server hostname.

high

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.paywb.com

medium

No PTR record for MX IP: 91.230.107.131

The IP 91.230.107.131 (for mail01.corp.wildberries.ru) has no reverse DNS record.

💡 Configure a PTR record for the mail server IP.

medium

No PTR record for MX IP: 91.230.107.132

The IP 91.230.107.132 (for mail02.corp.wildberries.ru) has no reverse DNS record.

💡 Configure a PTR record for the mail server IP.

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.paywb.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

Void lookup: a:exchangeost.corp.wildberries.ru

The mechanism a:exchangeost.corp.wildberries.ru returns no records, wasting a DNS lookup.

💡 Remove mechanisms that reference non-existent domains.

low

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@paywb.com").

low

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.

low

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"

low

SPF record length OK (252 bytes)

SPF record is within safe DNS packet size limits.

pass

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

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

Mail server port configuration is acceptable

No concerning port exposure detected.

pass

NS delegation is properly configured

All nameservers are responsive, consistent, and properly secured.

pass

DNS responses are consistent across all nameservers

All authoritative nameservers return consistent answers with proper AA flags.

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

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

Domain is IPv4-only

No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.

informational

RFC 8058 one-click unsubscribe assessment

No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.

informational

MX IP network diversity

All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.

informational

SOA record parameters

Serial: 261490819, Refresh: 120s, Retry: 90s, Expire: 1209600s, Min TTL: 300s

informational

Authorized certificate authorities

CAA records restrict certificate issuance to: letsencrypt.org, globalsign.com, comodoca.com, trust-provider.com, sectigo.com, certum.pl, usertrust.com, certum.eu

informational

Attack Surface Findings

Non-responsive IP for ns1.paywb.com: 91.230.107.26

The subdomain ns1.paywb.com resolves to 91.230.107.26 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 91.230.107.26 is operational or remove the DNS record for ns1.paywb.com.

medium

Non-responsive IP for ns2.paywb.com: 194.1.214.114

The subdomain ns2.paywb.com resolves to 194.1.214.114 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 194.1.214.114 is operational or remove the DNS record for ns2.paywb.com.

medium

Non-responsive IP for vpn.paywb.com: 91.230.107.24

The subdomain vpn.paywb.com resolves to 91.230.107.24 which is not responding on ports 80 or 443. This may indicate a decommissioned server.

💡 Verify the server at 91.230.107.24 is operational or remove the DNS record for vpn.paywb.com.

medium

Internal information in TXT record

A TXT record for paywb.com contains references to internal resources: corp.wildberries.ru, exchangedtln.corp, exchangeost.corp, exchangeost01.corp

💡 Remove internal hostnames and IP addresses from public TXT records.

medium

Internal information in TXT record

A TXT record for paywb.com contains references to internal resources: corp.wildberries.ru, exchangedtln.corp, exchangeost.corp, exchangeost01.corp

💡 Remove internal hostnames and IP addresses from public TXT records.

medium

DNS ANY query returns 24 record(s)

The DNS server responds to ANY queries with 24 record(s), creating significant DNS amplification risk.

💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.

medium

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.

medium

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

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 email autodiscovery endpoints detected

No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.

pass

40 subdomain(s) discovered for paywb.com

Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.

informational

289 certificate(s) found in CT logs

Certificate Transparency logs contain 289 certificate(s) for paywb.com and its subdomains. Each certificate reveals subdomain names.

informational

Reputation Findings

Missing domain locks: clientDeleteProhibited

Domain paywb.com is missing protective locks: clientDeleteProhibited.

💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.

high

Missing Strict-Transport-Security on paywb.com

The Strict-Transport-Security header is not set on https://paywb.com.

💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.

medium

Missing security.txt

No security.txt found at https://paywb.com/.well-known/security.txt.

💡 Create a /.well-known/security.txt file per RFC 9116 with Contact, Expires, and optionally Encryption and Policy fields.

low

Not listed on any DNS blacklists

Domain and MX IPs checked against 55 DNSBLs — no listings found.

pass

TLS certificate valid for 81 days

Certificate for paywb.com expires on 2026-08-19.

pass

Certificate issued by GlobalSign GCC R6 AlphaSSL CA 2025

The certificate for paywb.com is issued by a third-party CA.

pass

Signature algorithm: rsa-sha256

The certificate for paywb.com uses an acceptable signature algorithm.

pass

RSA key: 2048 bits

The certificate for paywb.com uses an adequate RSA key of 2048 bits.

pass

SCTs present in certificate

The certificate for paywb.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on paywb.com.

pass

Domain valid for 262 days

Domain paywb.com expires on 2027-02-15.

pass

No disposable email provider MX records

MX records for paywb.com do not match known disposable email provider patterns.

pass

Domain is 4485 days old

Domain paywb.com was registered 2014-02-15.

pass

No wildcard MX records

No wildcard MX records detected for paywb.com.

pass

TLD has good reputation

The .com TLD is not on known abuse watchlists.

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 (mx02.wildberries.ru) uses with cipher including Forward Secrecy.

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

Could not connect to webmail.paywb.com

HTTPS request to https://webmail.paywb.com failed or timed out.

informational

WHOIS registration data

Registrar: Regional Network Information Center, JSC dba RU-CENTER | Created: 2014-02-15 | Expires: 2027-02-15 | Updated: 2026-02-14

informational

WHOIS privacy protection not detected

Domain paywb.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.

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: pawb.com (has MX!), psywb.com (has MX!), payqb.com (has MX!), paysb.com (has MX!), payab.com (has MX!)

14 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 14. 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 missing

⚠️ DMARC policy is missing. Even with SPF configured, you lack the policy layer that tells receiving servers what to do with authentication failures.

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 missing

⚠️ 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: mail01.corp.wildberries.ru

PTR record proves mail server legitimacy

MX: mail01.corp.wildberries.ru Mail server at 91.230.107.131 → PTR Record No PTR record

⚠️ Mail server mail01.corp.wildberries.ru (91.230.107.131) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.

Mail Server Identity: mx01.wildberries.ru

PTR record proves mail server legitimacy

MX: mx01.wildberries.ru Mail server at 91.230.107.177 → PTR Record Reverse DNS: mx01.wildberries.ru

Mail Server Identity: mx02.wildberries.ru

PTR record proves mail server legitimacy

MX: mx02.wildberries.ru Mail server at 91.230.107.178 → PTR Record Reverse DNS: mx02.wildberries.ru

Mail Server Identity: mail03.corp.wildberries.ru

PTR record proves mail server legitimacy

MX: mail03.corp.wildberries.ru Mail server at 91.230.107.133 → PTR Record Reverse DNS: collectorbsd.wildberries.ru

Mail Server Identity: mx03.wildberries.ru

PTR record proves mail server legitimacy

MX: mx03.wildberries.ru Mail server at 91.230.107.183 → PTR Record Reverse DNS: mx03.wildberries.ru

Mail Server Identity: mail02.corp.wildberries.ru

PTR record proves mail server legitimacy

MX: mail02.corp.wildberries.ru Mail server at 91.230.107.132 → PTR Record No PTR record

⚠️ Mail server mail02.corp.wildberries.ru (91.230.107.132) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.

Mail Server Reputation: mail01.corp.wildberries.ru