Identity
11
D
armis.com
Posture Score: 65/100
Scanned May 8, 2026 at 5:14 PM UTC
Attack Surface
87
Reputation
96
Identity Findings
Overly broad CIDR range: 192.168.0.1/16
The /16 CIDR block authorizes a very large IP range to send email as this domain.
💡 Narrow the IP range to only the specific servers that send email.
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.
Weak DKIM RSA key (~1296 bits) for selector 's2'
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.
Port 465 open but TLS handshake failed on mailstream-east.mxrecord.io
Port 465 (SMTPS) is open but does not complete a TLS handshake.
💡 Ensure TLS is properly configured on port 465.
FCrDNS failure: no PTR for 172.65.213.128 (mailstream-east.mxrecord.io)
The IP 172.65.213.128 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.
FCrDNS failure: no PTR for 172.65.64.78 (mailstream-central.mxrecord.mx)
The IP 172.65.64.78 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.
FCrDNS failure: no PTR for 172.65.220.210 (mailstream-west.mxrecord.io)
The IP 172.65.220.210 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.
No PTR record for MX IP: 172.65.213.128
The IP 172.65.213.128 (for mailstream-east.mxrecord.io) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 172.65.64.78
The IP 172.65.64.78 (for mailstream-central.mxrecord.mx) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 172.65.220.210
The IP 172.65.220.210 (for mailstream-west.mxrecord.io) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
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.armis.com/.well-known/mta-sts.txt
ManageSieve port 4190 open on mailstream-east.mxrecord.io
Port 4190 (ManageSieve) is publicly accessible. This should typically be restricted.
💡 Restrict port 4190 access to authorized networks via firewall rules.
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 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@armis.com").
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"
Slow DNS response from ns-424.awsdns-53.com: 2070.8ms
The nameserver ns-424.awsdns-53.com responded in 2070.8ms, exceeding the 500ms threshold.
💡 Investigate network latency or performance issues on ns-424.awsdns-53.com.
Very low TTL on MX records: 272s
3 MX records have a TTL of 272s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on A records: 60s
2 A records have a TTL of 60s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 32s
38 TXT records have a TTL of 32s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 32s
The SPF record has a TTL of 32s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 273s
The DMARC record has a TTL of 273s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7173s) differs significantly from the authoritative zone (~172800s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
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.
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.
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 mailstream-east.mxrecord.io
Detected open mail-related ports: 25, 110, 143, 465, 587, 993, 995, 4190
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.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s
Authorized certificate authorities
CAA records restrict certificate issuance to: comodoca.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org, pki.goog; cansignhttpexchanges=yes, sectigo.com, ssl.com
Attack Surface Findings
Internal information in TXT record
A TXT record for armis.com contains references to internal resources: 192.168.0.1
💡 Remove internal hostnames and IP addresses from public TXT records.
DNS ANY query returns 49 record(s)
The DNS server responds to ANY queries with 49 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
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.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
5 subdomain(s) discovered for armis.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 armis.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.armis.com, resolving to 104.254.140.10, 104.254.140.246. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Reputation Findings
Missing Strict-Transport-Security on webmail.armis.com
The Strict-Transport-Security header is not set on https://webmail.armis.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
HSTS enabled with preload on armis.com
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
security.txt present
Found security.txt at https://armis.com/.well-known/security.txt.
TLS certificate valid for 80 days
Certificate for armis.com expires on 2026-07-27.
Certificate issued by E8
The certificate for armis.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for armis.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for armis.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for armis.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on armis.com.
Domain valid for 219 days
Domain armis.com expires on 2026-12-14.
Domain transfer and delete locks enabled
Domain armis.com has clientTransferProhibited and clientDeleteProhibited locks.
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 contact lookup failed
Could not query abuse contact information.
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: GoDaddy.com, LLC | Created: 2001-12-14 | Expires: 2026-12-14 | Updated: 2025-12-15
WHOIS privacy protection enabled
Domain armis.com has WHOIS privacy/redaction enabled.
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: mailstream-east.mxrecord.io
PTR record proves mail server legitimacy
MX: mailstream-east.mxrecord.io
Mail server at 172.65.213.128
→
PTR Record
No PTR record
⚠️ Mail server mailstream-east.mxrecord.io (172.65.213.128) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mailstream-central.mxrecord.mx
PTR record proves mail server legitimacy
MX: mailstream-central.mxrecord.mx
Mail server at 172.65.64.78
→
PTR Record
No PTR record
⚠️ Mail server mailstream-central.mxrecord.mx (172.65.64.78) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mailstream-west.mxrecord.io
PTR record proves mail server legitimacy
MX: mailstream-west.mxrecord.io
Mail server at 172.65.220.210
→
PTR Record
No PTR record
⚠️ Mail server mailstream-west.mxrecord.io (172.65.220.210) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: mailstream-east.mxrecord.io
RBL check ensures server is not blacklisted
MX: mailstream-east.mxrecord.io
Mail server at 172.65.213.128
→
RBL Status
Not blacklisted
Mail Server Reputation: mailstream-central.mxrecord.mx
RBL check ensures server is not blacklisted
MX: mailstream-central.mxrecord.mx
Mail server at 172.65.64.78
→
RBL Status
Not blacklisted
Mail Server Reputation: mailstream-west.mxrecord.io
RBL check ensures server is not blacklisted
MX: mailstream-west.mxrecord.io
Mail server at 172.65.220.210
→
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/armis.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan armis.com Again