Identity
31
F
inter-corporate.com
Posture Score: 44/100
Scanned May 15, 2026 at 5:17 AM UTC
Attack Surface
0
Reputation
100
Identity Findings
Nameserver unresponsive: fast09.inter-corporate.com
The nameserver fast09.inter-corporate.com is not responding on port 53.
💡 Verify that fast09.inter-corporate.com is properly configured and accessible.
Nameserver unresponsive: fast07.inter-corporate.com
The nameserver fast07.inter-corporate.com is not responding on port 53.
💡 Verify that fast07.inter-corporate.com is properly configured and accessible.
Nameserver unresponsive: fast04.inter-corporate.com
The nameserver fast04.inter-corporate.com is not responding on port 53.
💡 Verify that fast04.inter-corporate.com is properly configured and accessible.
Nameserver unresponsive: fast06.inter-corporate.com
The nameserver fast06.inter-corporate.com is not responding on port 53.
💡 Verify that fast06.inter-corporate.com is properly configured and accessible.
NS delegation mismatch
The registrar-delegated nameservers do not match the zone NS records.
💡 Update either the registrar NS delegation or the zone NS records to match.
Inconsistent DNS responses across nameservers
Authoritative nameservers return different answers for the same query.
💡 Verify zone transfers are working correctly and all nameservers serve the same zone data.
Generic ISP PTR hostname: 65.110.3.153.van970.dc.cipherkey.net
The PTR record for 65.110.3.153 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.inter-corporate.com
Generic ISP PTR hostname: 65.110.3.173.van970.dc.cipherkey.net
The PTR record for 65.110.3.173 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.inter-corporate.com
Generic ISP PTR hostname: 65.110.3.133.van970.dc.cipherkey.net
The PTR record for 65.110.3.133 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.inter-corporate.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.
No PTR record for IPv6 address: 2605:7c00:1:2:65:110:3:153
The IPv6 address 2605:7c00:1:2:65:110:3:153 for mail02.inter-corporate.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 2605:7c00:1:2:65:110:3:173
The IPv6 address 2605:7c00:1:2:65:110:3:173 for mail03.inter-corporate.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
No PTR record for IPv6 address: 2605:7c00:1:2:65:110:3:133
The IPv6 address 2605:7c00:1:2:65:110:3:133 for mail01.inter-corporate.com has no reverse DNS record.
💡 Configure a PTR record for the IPv6 address.
Unknown CAA tag: contactemail
The CAA record contains an unrecognized tag 'contactemail'.
💡 Review the CAA record and use standard tags (issue, issuewild, iodef).
Unknown CAA tag: contactphone
The CAA record contains an unrecognized tag 'contactphone'.
💡 Review the CAA record and use standard tags (issue, issuewild, iodef).
Slow DNS response from fast09.inter-corporate.com: 758.1ms
The nameserver fast09.inter-corporate.com responded in 758.1ms, exceeding the 500ms threshold.
💡 Investigate network latency or performance issues on fast09.inter-corporate.com.
Slow DNS response from fast07.inter-corporate.com: 765.4ms
The nameserver fast07.inter-corporate.com responded in 765.4ms, exceeding the 500ms threshold.
💡 Investigate network latency or performance issues on fast07.inter-corporate.com.
Slow DNS response from fast04.inter-corporate.com: 4219.7ms
The nameserver fast04.inter-corporate.com responded in 4219.7ms, exceeding the 500ms threshold.
💡 Investigate network latency or performance issues on fast04.inter-corporate.com.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (40 bytes)
SPF record is within safe DNS packet size limits.
DKIM records are valid
DKIM records found and validated for selectors: mail
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
No external DMARC report destinations
All DMARC report URIs point to the same domain — no external authorization needed.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
MX records are valid
All MX records are properly configured.
3 MX records with 3 unique IPs
Multiple MX records provide mail delivery redundancy.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
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.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
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=s, aspf=s
DKIM alignment is strict, SPF alignment is strict.
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
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: ri
The DMARC record contains tags deprecated in DMARCbis: ri. 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 VMC authority URL in BIMI record
The BIMI record does not specify a VMC (a= tag). Gmail and Apple Mail require a VMC to display brand logos.
Open mail ports on mail02.inter-corporate.com
Detected open mail-related ports: 25, 465
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: 1995033145, Refresh: 888s, Retry: 388s, Expire: 3888888s, Min TTL: 88s
Authorized certificate authorities
CAA records restrict certificate issuance to: letsencrypt.org
Attack Surface Findings
Non-responsive nameserver: fast09.inter-corporate.com
The nameserver fast09.inter-corporate.com delegated for inter-corporate.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to fast09.inter-corporate.com or ensure the nameserver is operational.
Non-responsive nameserver: fast07.inter-corporate.com
The nameserver fast07.inter-corporate.com delegated for inter-corporate.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to fast07.inter-corporate.com or ensure the nameserver is operational.
Non-responsive nameserver: fast04.inter-corporate.com
The nameserver fast04.inter-corporate.com delegated for inter-corporate.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to fast04.inter-corporate.com or ensure the nameserver is operational.
Non-responsive nameserver: fast06.inter-corporate.com
The nameserver fast06.inter-corporate.com delegated for inter-corporate.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to fast06.inter-corporate.com or ensure the nameserver is operational.
Non-responsive nameserver: fast01.inter-corporate.com
The nameserver fast01.inter-corporate.com delegated for inter-corporate.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to fast01.inter-corporate.com or ensure the nameserver is operational.
Non-responsive nameserver: fast02.inter-corporate.com
The nameserver fast02.inter-corporate.com delegated for inter-corporate.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to fast02.inter-corporate.com or ensure the nameserver is operational.
Non-responsive nameserver: fast00.inter-corporate.com
The nameserver fast00.inter-corporate.com delegated for inter-corporate.com is not responding on port 53. An attacker who gains control of this hostname could hijack the entire zone.
💡 Remove the NS delegation to fast00.inter-corporate.com or ensure the nameserver is operational.
Microsoft Autodiscover accessible without authentication
The Autodiscover endpoint at https://autodiscover.inter-corporate.com/autodiscover/autodiscover.xml returns configuration data without requiring authentication. This exposes email server details to unauthenticated users.
💡 Configure the Autodiscover endpoint to require authentication before returning configuration data.
Non-responsive IP for www.inter-corporate.com: 2605:7c00:1:2:65:110:3:187
The subdomain www.inter-corporate.com resolves to 2605:7c00:1:2:65:110:3:187 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2605:7c00:1:2:65:110:3:187 is operational or remove the DNS record for www.inter-corporate.com.
HINFO record exposes system information
An HINFO record for inter-corporate.com reveals hardware/OS details: CPU=Intel, OS=Debian. This aids attacker reconnaissance.
💡 Remove the HINFO record from public DNS. HINFO records are rarely needed and expose unnecessary system details.
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.
RP record exposes responsible person
An RP (Responsible Person) record for inter-corporate.com reveals contact information: noc.inter-corporate.com.. This can be used for social engineering.
💡 Remove the RP record if the contact information is not intended to be public.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.inter-corporate.com is publicly accessible and exposes mail server configuration details.
💡 Review the autoconfig XML to ensure it does not expose internal server names or sensitive configuration.
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.
17 subdomain(s) discovered for inter-corporate.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
106 certificate(s) found in CT logs
Certificate Transparency logs contain 106 certificate(s) for inter-corporate.com and its subdomains. Each certificate reveals subdomain names.
4 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
Reputation Findings
HSTS enabled with preload on inter-corporate.com
Strict-Transport-Security: max-age=32888888;includeSubDomains;preload
HSTS enabled with preload on webmail.inter-corporate.com
Strict-Transport-Security: max-age=32888888;includeSubDomains;preload
security.txt present
Found security.txt at https://inter-corporate.com/.well-known/security.txt.
TLS certificate valid for 51 days
Certificate for inter-corporate.com expires on 2026-07-05.
Certificate issued by R12
The certificate for inter-corporate.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for inter-corporate.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for inter-corporate.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for inter-corporate.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on inter-corporate.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 (mail03.inter-corporate.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner matches infrastructure identity
The SMTP banner (mail02.inter-corporate.com) aligns with the MX hostname (mail02.inter-corporate.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 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 lookup failed
Could not retrieve WHOIS data for inter-corporate.com.
Typosquat detected: intercorporate.com (has MX!)
1 registered lookalike domain(s) that could be used for phishing against your brand. 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: mail02.inter-corporate.com
PTR record proves mail server legitimacy
MX: mail02.inter-corporate.com
Mail server at 65.110.3.153
→
PTR Record
Reverse DNS: 65.110.3.153.van970.dc.cipherkey.net
Mail Server Identity: mail03.inter-corporate.com
PTR record proves mail server legitimacy
MX: mail03.inter-corporate.com
Mail server at 65.110.3.173
→
PTR Record
Reverse DNS: 65.110.3.173.van970.dc.cipherkey.net
Mail Server Identity: mail01.inter-corporate.com
PTR record proves mail server legitimacy
MX: mail01.inter-corporate.com
Mail server at 65.110.3.133
→
PTR Record
Reverse DNS: 65.110.3.133.van970.dc.cipherkey.net
Mail Server Reputation: mail02.inter-corporate.com
RBL check ensures server is not blacklisted
MX: mail02.inter-corporate.com
Mail server at 65.110.3.153
→
RBL Status
Not blacklisted
Mail Server Reputation: mail03.inter-corporate.com
RBL check ensures server is not blacklisted
MX: mail03.inter-corporate.com
Mail server at 65.110.3.173
→
RBL Status
Not blacklisted
Mail Server Reputation: mail01.inter-corporate.com
RBL check ensures server is not blacklisted
MX: mail01.inter-corporate.com
Mail server at 65.110.3.133
→
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
Mode: enforce
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:
<img src="https://scan.ractermx.com/badge/inter-corporate.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan inter-corporate.com Again