Identity
73
D
elcompanies.com
Posture Score: 60/100
Scanned May 17, 2026 at 9:30 PM UTC
Attack Surface
23
Reputation
84
Identity Findings
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.elcompanies.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.elcompanies.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"
Void lookup: include:%{ir}.%{v}.%{d}.spf.has.pphosted.com
The mechanism include:%{ir}.%{v}.%{d}.spf.has.pphosted.com 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@elcompanies.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.
Shared IP 67.231.153.71 used by multiple MX servers
The IP 67.231.153.71 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Very low TTL on MX records: 282s
2 MX records have a TTL of 282s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 283s
15 TXT records have a TTL of 283s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 283s
The SPF record has a TTL of 283s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record length OK (56 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.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
MX records are valid
All MX records are properly configured.
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 responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
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.
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.
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 mxa-001a2001.gslb.pphosted.com
Detected open mail-related ports: 25
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: 2404431052, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Non-responsive nameserver:
The nameserver delegated for elcompanies.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 or ensure the nameserver is operational.
Non-responsive nameserver:
The nameserver delegated for elcompanies.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 or ensure the nameserver is operational.
Non-responsive nameserver:
The nameserver delegated for elcompanies.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 or ensure the nameserver is operational.
NSEC records enable zone walking
The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.
💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
Non-responsive IP for www.elcompanies.com: 2606:4700::6812:d65
The subdomain www.elcompanies.com resolves to 2606:4700::6812:d65 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:d65 is operational or remove the DNS record for www.elcompanies.com.
Non-responsive IP for www.elcompanies.com: 2606:4700::6812:c65
The subdomain www.elcompanies.com resolves to 2606:4700::6812:c65 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:c65 is operational or remove the DNS record for www.elcompanies.com.
Non-responsive IP for ns2.elcompanies.com: 2400:cb00:2049:1::adf5:3a29
The subdomain ns2.elcompanies.com resolves to 2400:cb00:2049:1::adf5:3a29 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2400:cb00:2049:1::adf5:3a29 is operational or remove the DNS record for ns2.elcompanies.com.
Non-responsive IP for dev.elcompanies.com: 63.158.167.154
The subdomain dev.elcompanies.com resolves to 63.158.167.154 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 63.158.167.154 is operational or remove the DNS record for dev.elcompanies.com.
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.
3 subdomain(s) discovered for elcompanies.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 elcompanies.com and its subdomains. Each certificate reveals subdomain names.
1 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
Domain expires in 37 days
Domain elcompanies.com expires on 2026-06-24 (37 days).
💡 Renew the domain registration soon — it expires within 60 days. Enable auto-renewal if available.
DMARC reports sent to URL shortener domain
DMARC aggregate or forensic reports contain sensitive authentication metadata. Sending them to URL shortener domains indicates misconfiguration or a compromised record.
💡 Change DMARC rua/ruf addresses to a domain you control.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on elcompanies.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://elcompanies.com/.well-known/security.txt.
TLS certificate valid for 153 days
Certificate for elcompanies.com expires on 2026-10-17.
Certificate issued by Sectigo Public Server Authentication CA OV R36
The certificate for elcompanies.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for elcompanies.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for elcompanies.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for elcompanies.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on elcompanies.com.
Domain transfer and delete locks enabled
Domain elcompanies.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for elcompanies.com do not match known disposable email provider patterns.
Domain is 10188 days old
Domain elcompanies.com was registered 1998-06-25.
No wildcard MX records
No wildcard MX records detected for elcompanies.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 (mxa-001a2001.gslb.pphosted.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (mxa-001a2001.gslb.pphosted.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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.elcompanies.com
HTTPS request to https://webmail.elcompanies.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 1998-06-25 | Expires: 2026-06-24 | Updated: 2025-03-25
WHOIS privacy protection not detected
Domain elcompanies.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
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: lcompanies.com (has MX!), ecompanies.com (has MX!), lecompanies.com (has MX!), rlcompanies.com (has MX!), dlcompanies.com (has MX!)
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: mxa-001a2001.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxa-001a2001.gslb.pphosted.com
Mail server at 67.231.148.39
→
PTR Record
Reverse DNS: mx0a-001a2001.pphosted.com
Mail Server Identity: mxb-001a2001.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxb-001a2001.gslb.pphosted.com
Mail server at 67.231.148.39
→
PTR Record
Reverse DNS: mx0a-001a2001.pphosted.com
Mail Server Reputation: mxa-001a2001.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxa-001a2001.gslb.pphosted.com
Mail server at 67.231.148.39
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb-001a2001.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxb-001a2001.gslb.pphosted.com
Mail server at 67.231.148.39
→
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 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
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/elcompanies.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan elcompanies.com Again