Identity
75
C
infomaniak.com
Posture Score: 70/100
Scanned May 10, 2026 at 5:54 AM UTC
Score History
Attack Surface
67
Reputation
68
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.infomaniak.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.infomaniak.com/.well-known/mta-sts.txt
BIMI logo may not be SVG Tiny PS
The logo URL returns Content-Type: . BIMI requires SVG Tiny PS format.
💡 Ensure the logo is in SVG Tiny PS format.
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"
Single MX record — no redundancy
Only one MX record exists. If this mail server goes down, all inbound mail will bounce. Most production mail systems use 2+ MX records with different priorities.
💡 Add a secondary MX record with a higher priority number (e.g., priority 20) pointing to a backup mail server.
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@infomaniak.com").
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.
Very low TTL on NS records: 281s
2 NS records have a TTL of 281s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 281s
The DMARC record has a TTL of 281s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
SPF record length OK (133 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.
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.
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.
VMC URL is accessible
The BIMI VMC authority URL is reachable and returns a valid response.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
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.
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.
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.
DANE/TLSA configured for mta-gw.infomaniak.ch
TLSA records found and TLS certificate is available for verification.
Open mail ports on mta-gw.infomaniak.ch
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: 2026051031, Refresh: 900s, Retry: 900s, Expire: 604800s, Min TTL: 60s
Attack Surface Findings
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.
Microsoft Autodiscover accessible without authentication
The Autodiscover endpoint at https://autodiscover.infomaniak.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.
DNS ANY query returns 35 record(s)
The DNS server responds to ANY queries with 35 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
NSEC used instead of NSEC3 (zone enumeration possible)
The domain uses NSEC records for authenticated denial of existence. NSEC allows zone walking.
💡 Migrate from NSEC to NSEC3 to prevent zone enumeration.
Mozilla Autoconfig endpoint detected
The Autoconfig endpoint at autoconfig.infomaniak.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.
15 subdomain(s) discovered for infomaniak.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 infomaniak.com and its subdomains. Each certificate reveals subdomain names.
5 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 29 days
Domain infomaniak.com expires on 2026-06-09 (29 days).
💡 Renew the domain registration urgently — it expires within 30 days.
Missing domain locks: clientDeleteProhibited
Domain infomaniak.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
SMTP banner mismatch: smtp-3-9003.mail.infomaniak.ch
The SMTP banner identifies as 'smtp-3-9003.mail.infomaniak.ch' but the MX hostname is 'mta-gw.infomaniak.ch' and PTR resolves to 'mx01.infomaniak.ch'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (mta-gw.infomaniak.ch).
HSTS enabled but missing preload directive on infomaniak.com
Strict-Transport-Security: max-age=63072000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
HSTS enabled with preload on webmail.infomaniak.com
Strict-Transport-Security: max-age=63072000; preload
security.txt present
Found security.txt at https://infomaniak.com/.well-known/security.txt.
TLS certificate valid for 291 days
Certificate for infomaniak.com expires on 2027-02-25.
Certificate issued by Sectigo Public Server Authentication CA DV R36
The certificate for infomaniak.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for infomaniak.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for infomaniak.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for infomaniak.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on infomaniak.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 (mta-gw.infomaniak.ch) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
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: Infomaniak Network SA | Created: 1997-06-10 | Expires: 2026-06-09 | Updated: 2025-06-02
WHOIS privacy protection enabled
Domain infomaniak.com has WHOIS privacy/redaction enabled.
Typosquat detected: infomanak.com (has MX!), infomania.com (has MX!), infoamniak.com (has MX!), infomanaik.com (has MX!), imfomaniak.com (has MX!)
6 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 6. 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: mta-gw.infomaniak.ch
PTR record proves mail server legitimacy
MX: mta-gw.infomaniak.ch
Mail server at 83.166.143.57
→
PTR Record
Reverse DNS: mx01.infomaniak.ch
Mail Server Reputation: mta-gw.infomaniak.ch
RBL check ensures server is not blacklisted
MX: mta-gw.infomaniak.ch
Mail server at 83.166.143.57
→
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/infomaniak.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan infomaniak.com Again