Identity
0
F
qnity.com
Posture Score: 49/100
Scanned May 18, 2026 at 2:55 AM UTC
Attack Surface
92
Reputation
54
Identity Findings
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.qnity.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@qnity.com").
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.
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.qnity.com
No STARTTLS support on mx10.mailspamprotection.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mx20.mailspamprotection.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mx30.mailspamprotection.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
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.
Port 465 open but TLS handshake failed on mx10.mailspamprotection.com
Port 465 (SMTPS) is open but does not complete a TLS handshake.
💡 Ensure TLS is properly configured on port 465.
Cannot check DNS consistency — no NS records
No nameserver records could be retrieved for consistency checking.
💡 Ensure NS records are properly configured.
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.qnity.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.
Generic ISP PTR hostname: 66.79.149.34.bc.googleusercontent.com
The PTR record for 34.149.79.66 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.qnity.com
Generic ISP PTR hostname: 61.156.120.34.bc.googleusercontent.com
The PTR record for 34.120.156.61 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.qnity.com
Generic ISP PTR hostname: 216.121.111.34.bc.googleusercontent.com
The PTR record for 34.111.121.216 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.qnity.com
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"
Void lookup: include:_0f1ad595d8fcd9f313fc7ff7e428b44f.spf.dnssmarthost.net
The mechanism include:_0f1ad595d8fcd9f313fc7ff7e428b44f.spf.dnssmarthost.net returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
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@qnity.com").
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.
SPF record length OK (99 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.
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.
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.
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 mx10.mailspamprotection.com
Detected open mail-related ports: 25, 465, 587
Domain is IPv4-only
No AAAA records found for the domain, MX servers, or nameservers. The domain operates on IPv4 only.
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
MX IPs span 3 different /16 networks, providing good diversity.
SOA record parameters
Serial: 1712250035, Refresh: 43200s, Retry: 7200s, Expire: 1209600s, Min TTL: 3600s
Attack Surface Findings
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.
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.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
4 subdomain(s) discovered for qnity.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
135 certificate(s) found in CT logs
Certificate Transparency logs contain 135 certificate(s) for qnity.com and its subdomains. Each certificate reveals subdomain names.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.qnity.com responded with HTTP 404.
Reputation Findings
Listed on dnsbl-2.uceprotect.net
34.149.79.66 (mx10.mailspamprotection.com) is listed on blacklist dnsbl-2.uceprotect.net (response: 127.0.0.2).
💡 Visit the dnsbl-2.uceprotect.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
34.149.79.66 (mx10.mailspamprotection.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
34.120.156.61 (mx20.mailspamprotection.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
HSTS enabled but missing preload directive on qnity.com
Strict-Transport-Security: max-age=15552000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://qnity.com/.well-known/security.txt.
TLS certificate valid for 33 days
Certificate for qnity.com expires on 2026-06-20.
Certificate issued by R12
The certificate for qnity.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for qnity.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for qnity.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for qnity.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on qnity.com.
Domain valid for 306 days
Domain qnity.com expires on 2027-03-20.
Domain transfer and delete locks enabled
Domain qnity.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for qnity.com do not match known disposable email provider patterns.
Domain is 9189 days old
Domain qnity.com was registered 2001-03-20.
No wildcard MX records
No wildcard MX records detected for qnity.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mx10.mailspamprotection.com) uses with cipher 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.qnity.com
HTTPS request to https://webmail.qnity.com failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 2001-03-20 | Expires: 2027-03-20 | Updated: 2026-03-21
WHOIS privacy protection enabled
Domain qnity.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: nity.com (has MX!), qinty.com (has MX!), anity.com (has MX!), qnty.com, qniy.com
10 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 10. 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 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: mx10.mailspamprotection.com
PTR record proves mail server legitimacy
MX: mx10.mailspamprotection.com
Mail server at 34.149.79.66
→
PTR Record
Reverse DNS: 66.79.149.34.bc.googleusercontent.com
Mail Server Identity: mx20.mailspamprotection.com
PTR record proves mail server legitimacy
MX: mx20.mailspamprotection.com
Mail server at 34.120.156.61
→
PTR Record
Reverse DNS: 61.156.120.34.bc.googleusercontent.com
Mail Server Identity: mx30.mailspamprotection.com
PTR record proves mail server legitimacy
MX: mx30.mailspamprotection.com
Mail server at 34.111.121.216
→
PTR Record
Reverse DNS: 216.121.111.34.bc.googleusercontent.com
Mail Server Reputation: mx10.mailspamprotection.com
RBL check ensures server is not blacklisted
MX: mx10.mailspamprotection.com
Mail server at 34.149.79.66
→
RBL Status
Not blacklisted
Mail Server Reputation: mx20.mailspamprotection.com
RBL check ensures server is not blacklisted
MX: mx20.mailspamprotection.com
Mail server at 34.120.156.61
→
RBL Status
Not blacklisted
Mail Server Reputation: mx30.mailspamprotection.com
RBL check ensures server is not blacklisted
MX: mx30.mailspamprotection.com
Mail server at 34.111.121.216
→
RBL Status
Not blacklisted
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 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
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/qnity.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan qnity.com Again