Identity
76
F
flightradar24.com
Posture Score: 56/100
Scanned May 29, 2026 at 1:45 AM UTC
Attack Surface
0
Reputation
92
Identity Findings
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.
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.flightradar24.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"
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@flightradar24.com").
Very low TTL on MX records: 120s
7 MX records have a TTL of 120s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 120s
7 TXT records have a TTL of 120s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 120s
The SPF record has a TTL of 120s 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 (37 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.
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).
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
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.
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.
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.
Shared/free email hosting detected: aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
Shared/free email hosting detected: alt1.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
Shared/free email hosting detected: alt2.aspmx.l.google.com
The MX record points to a known shared or free email hosting provider.
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 aspmx.l.google.com
Detected open mail-related ports: 25
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
MX IPs span 5 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2404871972, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Non-responsive IP for www.flightradar24.com: 2606:4700::6812:6270
The subdomain www.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for www.flightradar24.com.
Non-responsive IP for www.flightradar24.com: 2606:4700::6812:6170
The subdomain www.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for www.flightradar24.com.
Non-responsive IP for ftp.flightradar24.com: 2606:4700::6812:6170
The subdomain ftp.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for ftp.flightradar24.com.
Non-responsive IP for ftp.flightradar24.com: 2606:4700::6812:6270
The subdomain ftp.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for ftp.flightradar24.com.
Non-responsive IP for ns1.flightradar24.com: 2606:4700::6812:6170
The subdomain ns1.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for ns1.flightradar24.com.
Non-responsive IP for ns1.flightradar24.com: 2606:4700::6812:6270
The subdomain ns1.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for ns1.flightradar24.com.
Non-responsive IP for ns2.flightradar24.com: 2606:4700::6812:6170
The subdomain ns2.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for ns2.flightradar24.com.
Non-responsive IP for ns2.flightradar24.com: 2606:4700::6812:6270
The subdomain ns2.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for ns2.flightradar24.com.
Non-responsive IP for vpn.flightradar24.com: 2606:4700::6812:6170
The subdomain vpn.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for vpn.flightradar24.com.
Non-responsive IP for vpn.flightradar24.com: 2606:4700::6812:6270
The subdomain vpn.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for vpn.flightradar24.com.
Non-responsive IP for remote.flightradar24.com: 2606:4700::6812:6170
The subdomain remote.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for remote.flightradar24.com.
Non-responsive IP for remote.flightradar24.com: 2606:4700::6812:6270
The subdomain remote.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for remote.flightradar24.com.
Non-responsive IP for admin.flightradar24.com: 2606:4700::6812:6170
The subdomain admin.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for admin.flightradar24.com.
Non-responsive IP for admin.flightradar24.com: 2606:4700::6812:6270
The subdomain admin.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for admin.flightradar24.com.
Non-responsive IP for portal.flightradar24.com: 2606:4700::6812:6270
The subdomain portal.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for portal.flightradar24.com.
Non-responsive IP for portal.flightradar24.com: 2606:4700::6812:6170
The subdomain portal.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for portal.flightradar24.com.
Non-responsive IP for dev.flightradar24.com: 2606:4700::6812:6270
The subdomain dev.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for dev.flightradar24.com.
Non-responsive IP for dev.flightradar24.com: 2606:4700::6812:6170
The subdomain dev.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for dev.flightradar24.com.
Non-responsive IP for staging.flightradar24.com: 2606:4700::6812:6170
The subdomain staging.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for staging.flightradar24.com.
Non-responsive IP for staging.flightradar24.com: 2606:4700::6812:6270
The subdomain staging.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for staging.flightradar24.com.
Non-responsive IP for test.flightradar24.com: 2606:4700::6812:6270
The subdomain test.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for test.flightradar24.com.
Non-responsive IP for test.flightradar24.com: 2606:4700::6812:6170
The subdomain test.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for test.flightradar24.com.
Non-responsive IP for api.flightradar24.com: 2606:4700::6812:6170
The subdomain api.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for api.flightradar24.com.
Non-responsive IP for api.flightradar24.com: 2606:4700::6812:6270
The subdomain api.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for api.flightradar24.com.
Non-responsive IP for app.flightradar24.com: 2606:4700::6812:6270
The subdomain app.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for app.flightradar24.com.
Non-responsive IP for app.flightradar24.com: 2606:4700::6812:6170
The subdomain app.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for app.flightradar24.com.
Non-responsive IP for cdn.flightradar24.com: 2606:4700::6812:6270
The subdomain cdn.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for cdn.flightradar24.com.
Non-responsive IP for cdn.flightradar24.com: 2606:4700::6812:6170
The subdomain cdn.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for cdn.flightradar24.com.
Non-responsive IP for blog.flightradar24.com: 2606:4700::6812:6170
The subdomain blog.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for blog.flightradar24.com.
Non-responsive IP for blog.flightradar24.com: 2606:4700::6812:6270
The subdomain blog.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for blog.flightradar24.com.
Non-responsive IP for shop.flightradar24.com: 2606:4700::6812:6270
The subdomain shop.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for shop.flightradar24.com.
Non-responsive IP for shop.flightradar24.com: 2606:4700::6812:6170
The subdomain shop.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for shop.flightradar24.com.
Non-responsive IP for store.flightradar24.com: 2606:4700::6812:6270
The subdomain store.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for store.flightradar24.com.
Non-responsive IP for store.flightradar24.com: 2606:4700::6812:6170
The subdomain store.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for store.flightradar24.com.
Non-responsive IP for support.flightradar24.com: 2606:4700::6812:6170
The subdomain support.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for support.flightradar24.com.
Non-responsive IP for support.flightradar24.com: 2606:4700::6812:6270
The subdomain support.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for support.flightradar24.com.
Non-responsive IP for help.flightradar24.com: 2606:4700::6812:6170
The subdomain help.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for help.flightradar24.com.
Non-responsive IP for help.flightradar24.com: 2606:4700::6812:6270
The subdomain help.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for help.flightradar24.com.
Non-responsive IP for docs.flightradar24.com: 2606:4700::6812:6270
The subdomain docs.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for docs.flightradar24.com.
Non-responsive IP for docs.flightradar24.com: 2606:4700::6812:6170
The subdomain docs.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for docs.flightradar24.com.
Non-responsive IP for status.flightradar24.com: 2606:4700::6812:6270
The subdomain status.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for status.flightradar24.com.
Non-responsive IP for status.flightradar24.com: 2606:4700::6812:6170
The subdomain status.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for status.flightradar24.com.
Non-responsive IP for git.flightradar24.com: 2606:4700::6812:6270
The subdomain git.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for git.flightradar24.com.
Non-responsive IP for git.flightradar24.com: 2606:4700::6812:6170
The subdomain git.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for git.flightradar24.com.
Non-responsive IP for ci.flightradar24.com: 2606:4700::6812:6170
The subdomain ci.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for ci.flightradar24.com.
Non-responsive IP for ci.flightradar24.com: 2606:4700::6812:6270
The subdomain ci.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for ci.flightradar24.com.
Non-responsive IP for jenkins.flightradar24.com: 2606:4700::6812:6170
The subdomain jenkins.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for jenkins.flightradar24.com.
Non-responsive IP for jenkins.flightradar24.com: 2606:4700::6812:6270
The subdomain jenkins.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for jenkins.flightradar24.com.
Non-responsive IP for grafana.flightradar24.com: 2606:4700::6812:6170
The subdomain grafana.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for grafana.flightradar24.com.
Non-responsive IP for grafana.flightradar24.com: 2606:4700::6812:6270
The subdomain grafana.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for grafana.flightradar24.com.
Non-responsive IP for prometheus.flightradar24.com: 2606:4700::6812:6270
The subdomain prometheus.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for prometheus.flightradar24.com.
Non-responsive IP for prometheus.flightradar24.com: 2606:4700::6812:6170
The subdomain prometheus.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for prometheus.flightradar24.com.
Non-responsive IP for kibana.flightradar24.com: 2606:4700::6812:6270
The subdomain kibana.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for kibana.flightradar24.com.
Non-responsive IP for kibana.flightradar24.com: 2606:4700::6812:6170
The subdomain kibana.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for kibana.flightradar24.com.
Non-responsive IP for elastic.flightradar24.com: 2606:4700::6812:6270
The subdomain elastic.flightradar24.com resolves to 2606:4700::6812:6270 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6270 is operational or remove the DNS record for elastic.flightradar24.com.
Non-responsive IP for elastic.flightradar24.com: 2606:4700::6812:6170
The subdomain elastic.flightradar24.com resolves to 2606:4700::6812:6170 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:6170 is operational or remove the DNS record for elastic.flightradar24.com.
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.
0 subdomain(s) discovered for flightradar24.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 flightradar24.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.flightradar24.com, resolving to 104.18.97.112, 104.18.98.112. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.flightradar24.com is active and requires authentication.
Reputation Findings
Missing Strict-Transport-Security on flightradar24.com
The Strict-Transport-Security header is not set on https://flightradar24.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.flightradar24.com
The Strict-Transport-Security header is not set on https://webmail.flightradar24.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
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://flightradar24.com/.well-known/security.txt.
TLS certificate valid for 71 days
Certificate for flightradar24.com expires on 2026-08-08.
Certificate issued by WE1
The certificate for flightradar24.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for flightradar24.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for flightradar24.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for flightradar24.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on flightradar24.com.
Domain valid for 217 days
Domain flightradar24.com expires on 2027-01-01.
Domain transfer and delete locks enabled
Domain flightradar24.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for flightradar24.com do not match known disposable email provider patterns.
Domain is 6043 days old
Domain flightradar24.com was registered 2009-11-10.
No wildcard MX records
No wildcard MX records detected for flightradar24.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 (aspmx.l.google.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (aspmx.l.google.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.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 2009-11-10 | Expires: 2027-01-01 | Updated: 2026-01-02
WHOIS privacy protection enabled
Domain flightradar24.com has WHOIS privacy/redaction enabled.
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: fightradar24.com (has MX!), flghtradar24.com (has MX!), flighradar24.com (has MX!), flightadar24.com (has MX!), flightrdar24.com (has MX!)
25 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 25. 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: aspmx.l.google.com
PTR record proves mail server legitimacy
MX: aspmx.l.google.com
Mail server at 209.85.202.26
→
PTR Record
Reverse DNS: dg-in-f26.1e100.net
Mail Server Identity: alt1.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt1.aspmx.l.google.com
Mail server at 173.194.76.27
→
PTR Record
Reverse DNS: ws-in-f27.1e100.net
Mail Server Identity: alt2.aspmx.l.google.com
PTR record proves mail server legitimacy
MX: alt2.aspmx.l.google.com
Mail server at 142.250.102.27
→
PTR Record
Reverse DNS: rb-in-f27.1e100.net
Mail Server Identity: aspmx2.googlemail.com
PTR record proves mail server legitimacy
MX: aspmx2.googlemail.com
Mail server at 173.194.76.26
→
PTR Record
Reverse DNS: ws-in-f26.1e100.net
Mail Server Identity: aspmx3.googlemail.com
PTR record proves mail server legitimacy
MX: aspmx3.googlemail.com
Mail server at 142.250.102.26
→
PTR Record
Reverse DNS: rb-in-f26.1e100.net
Mail Server Identity: aspmx4.googlemail.com
PTR record proves mail server legitimacy
MX: aspmx4.googlemail.com
Mail server at 192.178.213.27
→
PTR Record
Reverse DNS: yugrqzs-in-f27.1e100.net
Mail Server Identity: aspmx5.googlemail.com
PTR record proves mail server legitimacy
MX: aspmx5.googlemail.com
Mail server at 142.251.127.27
→
PTR Record
Reverse DNS: lcfrai-in-f27.1e100.net
Mail Server Reputation: aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: aspmx.l.google.com
Mail server at 209.85.202.26
→
RBL Status
Not blacklisted
Mail Server Reputation: alt1.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt1.aspmx.l.google.com
Mail server at 173.194.76.27
→
RBL Status
Not blacklisted
Mail Server Reputation: alt2.aspmx.l.google.com
RBL check ensures server is not blacklisted
MX: alt2.aspmx.l.google.com
Mail server at 142.250.102.27
→
RBL Status
Not blacklisted
Mail Server Reputation: aspmx2.googlemail.com
RBL check ensures server is not blacklisted
MX: aspmx2.googlemail.com
Mail server at 173.194.76.26
→
RBL Status
Not blacklisted
Mail Server Reputation: aspmx3.googlemail.com
RBL check ensures server is not blacklisted
MX: aspmx3.googlemail.com
Mail server at 142.250.102.26
→
RBL Status
Not blacklisted
Mail Server Reputation: aspmx4.googlemail.com
RBL check ensures server is not blacklisted
MX: aspmx4.googlemail.com
Mail server at 192.178.213.27
→
RBL Status
Not blacklisted
Mail Server Reputation: aspmx5.googlemail.com
RBL check ensures server is not blacklisted
MX: aspmx5.googlemail.com
Mail server at 142.251.127.27
→
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/flightradar24.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan flightradar24.com Again