Identity
81
B
ultimate-guitar.com
Posture Score: 85/100
Scanned May 28, 2026 at 2:19 AM UTC
Attack Surface
95
Reputation
80
Identity Findings
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.
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.ultimate-guitar.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 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@ultimate-guitar.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 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"
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (73 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.
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.
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.
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.
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=r
DKIM alignment is strict, 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.
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 mx9.ultimate-guitar.com
Detected open mail-related ports: 25, 110, 143, 465, 587, 993, 995
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: 2404950394, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Authorized certificate authorities
CAA records restrict certificate issuance to: ssl.com, pki.goog; cansignhttpexchanges=yes, amazonaws.com, digicert.com; cansignhttpexchanges=yes, comodoca.com, letsencrypt.org
Attack Surface Findings
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.
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.
6 subdomain(s) discovered for ultimate-guitar.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 ultimate-guitar.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.ultimate-guitar.com, resolving to 178.18.22.152. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected
The Autodiscover endpoint at autodiscover.ultimate-guitar.com responded with HTTP 404.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain ultimate-guitar.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
Missing Strict-Transport-Security on ultimate-guitar.com
The Strict-Transport-Security header is not set on https://ultimate-guitar.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Missing Strict-Transport-Security on webmail.ultimate-guitar.com
The Strict-Transport-Security header is not set on https://webmail.ultimate-guitar.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
Weak TLS configuration on primary MX
The primary MX server supports deprecated TLS versions or weak cipher suites: No Forward Secrecy (PFS): AES128-SHA. Modern receivers penalize reputation for lack of strong encryption.
💡 Disable TLS 1.0/1.1, remove weak ciphers (RC4, 3DES), and ensure Forward Secrecy (ECDHE) is preferred.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://ultimate-guitar.com/.well-known/security.txt.
TLS certificate valid for 59 days
Certificate for ultimate-guitar.com expires on 2026-07-26.
Certificate issued by WE1
The certificate for ultimate-guitar.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for ultimate-guitar.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for ultimate-guitar.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for ultimate-guitar.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on ultimate-guitar.com.
Domain valid for 3060 days
Domain ultimate-guitar.com expires on 2034-10-13.
No disposable email provider MX records
MX records for ultimate-guitar.com do not match known disposable email provider patterns.
Domain is 9723 days old
Domain ultimate-guitar.com was registered 1999-10-13.
No wildcard MX records
No wildcard MX records detected for ultimate-guitar.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.
SMTP banner matches infrastructure identity
The SMTP banner (mail.ultimate-guitar.com) aligns with the MX hostname (mx9.ultimate-guitar.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 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.
WHOIS registration data
Registrar: Network Solutions, LLC | Created: 1999-10-13 | Expires: 2034-10-13 | Updated: 2025-09-08
WHOIS privacy protection not detected
Domain ultimate-guitar.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: utimate-guitar.com (has MX!), ulimate-guitar.com (has MX!), ultmate-guitar.com (has MX!), ultimat-guitar.com (has MX!), ultimateguitar.com (has MX!)
9 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 9. 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: mx9.ultimate-guitar.com
PTR record proves mail server legitimacy
MX: mx9.ultimate-guitar.com
Mail server at 178.18.22.145
→
PTR Record
Reverse DNS: mx9.ultimate-guitar.com
Mail Server Reputation: mx9.ultimate-guitar.com
RBL check ensures server is not blacklisted
MX: mx9.ultimate-guitar.com
Mail server at 178.18.22.145
→
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-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/ultimate-guitar.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan ultimate-guitar.com Again