← Back to Scanner
D

doctorondemand.com

Posture Score: 63/100

Scanned May 8, 2026 at 5:08 PM UTC

Identity

0

Attack Surface

91

Reputation

98

Identity Findings

Invalid DKIM syntax for selector 'default'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
Invalid DKIM syntax for selector 'selector1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
Invalid DKIM syntax for selector 'selector2'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
Weak DKIM RSA key (~1296 bits) for selector 'google'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
high
Invalid DKIM syntax for selector 'dkim'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
Invalid DKIM syntax for selector 'mail'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
Weak DKIM RSA key (~1296 bits) for selector 'k1'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
high
Invalid DKIM syntax for selector 's1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
Invalid DKIM syntax for selector 's2'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
Invalid DKIM syntax for selector 'mandrill'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
Invalid DKIM syntax for selector 'amazonses'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
Invalid DKIM syntax for selector 'cm'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
Invalid DKIM syntax for selector 'smtp'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
high
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.doctorondemand.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@doctorondemand.com").
low
SPF has ip4 mechanisms but no ip6
The SPF record authorizes IPv4 addresses but not IPv6. Your MX servers have AAAA records, so IPv6 mail delivery is possible without SPF authorization.
💡 Add ip6: mechanisms to the SPF record for your IPv6 mail server addresses.
low
Shared IP 173.194.76.26 used by multiple MX servers
The IP 173.194.76.26 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
low
Shared IP 142.250.102.27 used by multiple MX servers
The IP 142.250.102.27 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
low
Very low TTL on A record: 35s
The A record has a TTL of 35s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on NS records: 34s
4 NS records have a TTL of 34s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on TXT records: 43s
19 TXT records have a TTL of 43s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on SPF record: 43s
The SPF record has a TTL of 43s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on DMARC record: 274s
The DMARC record has a TTL of 274s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
pass
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
pass
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
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
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
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
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
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: 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
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 3 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

DNS ANY query returns 31 record(s)
The DNS server responds to ANY queries with 31 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
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
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
low
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
pass
3 subdomain(s) discovered for doctorondemand.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
informational
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for doctorondemand.com and its subdomains. Each certificate reveals subdomain names.
informational
Wildcard DNS record detected
A wildcard DNS record exists for *.doctorondemand.com, resolving to 162.159.135.42. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
informational
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.doctorondemand.com is active and requires authentication.
informational

Reputation Findings

HSTS enabled but missing preload directive on doctorondemand.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
low
HSTS enabled but missing preload directive on webmail.doctorondemand.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
low
security.txt present
Found security.txt at https://doctorondemand.com/.well-known/security.txt.
pass
TLS certificate valid for 34 days
Certificate for doctorondemand.com expires on 2026-06-12.
pass
Certificate issued by WE1
The certificate for doctorondemand.com is issued by a third-party CA.
pass
Signature algorithm: ecdsa-with-sha256
The certificate for doctorondemand.com uses an acceptable signature algorithm.
pass
ECC key: 256 bits
The certificate for doctorondemand.com uses an adequate ECC key of 256 bits.
pass
SCTs present in certificate
The certificate for doctorondemand.com contains Signed Certificate Timestamps.
pass
No weak ciphers detected
No known weak cipher suites detected on doctorondemand.com.
pass
Domain valid for 145 days
Domain doctorondemand.com expires on 2026-09-30.
pass
Domain transfer and delete locks enabled
Domain doctorondemand.com has clientTransferProhibited and clientDeleteProhibited locks.
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 contact lookup failed
Could not query abuse contact information.
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: 2003-09-30 | Expires: 2026-09-30 | Updated: 2025-10-01
informational
WHOIS privacy protection enabled
Domain doctorondemand.com has WHOIS privacy/redaction enabled.
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: reject
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: reject
Mail Server Identity: aspmx.l.google.com
PTR record proves mail server legitimacy
MX: aspmx.l.google.com Mail server at 209.85.202.27 → PTR Record Reverse DNS: dg-in-f27.1e100.net
Mail Server Identity: aspmx2.googlemail.com
PTR record proves mail server legitimacy
MX: aspmx2.googlemail.com Mail server at 173.194.76.26 → PTR Record Reverse DNS: ws-in-f26.1e100.net
Mail Server Identity: aspmx3.googlemail.com
PTR record proves mail server legitimacy
MX: aspmx3.googlemail.com Mail server at 142.250.102.27 → PTR Record Reverse DNS: rb-in-f27.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.27 → RBL Status Not blacklisted
Mail Server Reputation: aspmx2.googlemail.com
RBL check ensures server is not blacklisted
MX: aspmx2.googlemail.com Mail server at 173.194.76.26 → RBL Status Not blacklisted
Mail Server Reputation: aspmx3.googlemail.com
RBL check ensures server is not blacklisted
MX: aspmx3.googlemail.com Mail server at 142.250.102.27 → 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: reject → BIMI Record Brand logo configured
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:

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

Want to re-scan this domain for updated results?

Scan doctorondemand.com Again