Identity
73
B
userapi.com
Posture Score: 82/100
Scanned May 27, 2026 at 3:02 PM UTC
Attack Surface
82
Reputation
90
Identity Findings
Invalid TLS certificate on mx.vk.com
The TLS certificate presented by the mail server is expired or invalid.
💡 Renew or replace the TLS certificate on the mail server.
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.userapi.com
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.userapi.com/.well-known/mta-sts.txt
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.
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@userapi.com").
Slow DNS response from ns3.vkontakte.ru: 2140.2ms
The nameserver ns3.vkontakte.ru responded in 2140.2ms, exceeding the 2000ms threshold.
💡 Investigate network latency or performance issues on ns3.vkontakte.ru.
Slow DNS response from ns2.vkontakte.ru: 2121ms
The nameserver ns2.vkontakte.ru responded in 2121ms, exceeding the 2000ms threshold.
💡 Investigate network latency or performance issues on ns2.vkontakte.ru.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (11 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.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
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.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
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.
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.
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 mx.vk.com
Detected open mail-related ports: 25, 143, 465, 993
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: 3567511290, Refresh: 900s, Retry: 600s, Expire: 604800s, Min TTL: 7200s
Attack Surface Findings
Non-responsive IP for ns1.userapi.com: 2a00:bdc0:ff:1::2
The subdomain ns1.userapi.com resolves to 2a00:bdc0:ff:1::2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:bdc0:ff:1::2 is operational or remove the DNS record for ns1.userapi.com.
Non-responsive IP for ns2.userapi.com: 93.186.224.100
The subdomain ns2.userapi.com resolves to 93.186.224.100 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 93.186.224.100 is operational or remove the DNS record for ns2.userapi.com.
Non-responsive IP for ns2.userapi.com: 2a00:bdc0:ff:2::2
The subdomain ns2.userapi.com resolves to 2a00:bdc0:ff:2::2 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a00:bdc0:ff:2::2 is operational or remove the DNS record for ns2.userapi.com.
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.
DNS ANY query returns 17 record(s)
The DNS server responds to ANY queries with 17 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
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.
4 subdomain(s) discovered for userapi.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 userapi.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.userapi.com, resolving to 87.240.129.187, 87.240.190.64. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.userapi.com responded with HTTP 418.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain userapi.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 userapi.com
Strict-Transport-Security: max-age=15768000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
HSTS enabled but missing preload directive on webmail.userapi.com
Strict-Transport-Security: max-age=15768000
💡 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://userapi.com/.well-known/security.txt.
TLS certificate valid for 304 days
Certificate for userapi.com expires on 2027-03-28.
Certificate issued by GlobalSign ECC OV SSL CA 2018
The certificate for userapi.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for userapi.com uses an acceptable signature algorithm.
ECC key: 384 bits
The certificate for userapi.com uses an adequate ECC key of 384 bits.
SCTs present in certificate
The certificate for userapi.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on userapi.com.
Domain valid for 120 days
Domain userapi.com expires on 2026-09-24.
No disposable email provider MX records
MX records for userapi.com do not match known disposable email provider patterns.
Domain is 6453 days old
Domain userapi.com was registered 2008-09-24.
No wildcard MX records
No wildcard MX records detected for userapi.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 (mx.vk.com) uses TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mx.vk.com) aligns with the MX hostname (mx.vk.com).
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: Regional Network Information Center, JSC dba RU-CENTER | Created: 2008-09-24 | Expires: 2026-09-24 | Updated: 2025-09-23
WHOIS privacy protection enabled
Domain userapi.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: serapi.com (has MX!), userpi.com (has MX!), userai.com (has MX!), userap.com (has MX!), useapi.com
6 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 6. 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 missing
→
DMARC Policy
DMARC policy: reject
⚠️ 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: mx.vk.com
PTR record proves mail server legitimacy
MX: mx.vk.com
Mail server at 87.240.169.121
→
PTR Record
Reverse DNS: mx.vk.com
Mail Server Reputation: mx.vk.com
RBL check ensures server is not blacklisted
MX: mx.vk.com
Mail server at 87.240.169.121
→
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: reject
→
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:
<img src="https://scan.ractermx.com/badge/userapi.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan userapi.com Again