Identity
33
F
faphouse2.com
Posture Score: 40/100
Scanned May 27, 2026 at 10:11 PM UTC
Attack Surface
0
Reputation
87
Identity Findings
No SPF record found
The domain has no SPF record, allowing anyone to send email as this domain.
💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.faphouse2.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@faphouse2.com").
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: Neither SPF nor DKIM is configured (at least one required); No DMARC record published (required since Feb 2024); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.faphouse2.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.faphouse2.com/.well-known/mta-sts.txt
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@faphouse2.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
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.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open relay check skipped — no MX records
Cannot test for open relay without MX records.
SMTP compliance check skipped — no MX records
Cannot test SMTP compliance without MX records.
Port exposure check skipped — no MX records
Cannot scan ports without MX records.
STARTTLS downgrade check skipped — no MX records
Cannot test STARTTLS without MX records.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 2402931114, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
Non-responsive IP for www.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain www.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for www.faphouse2.com.
Non-responsive IP for www.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain www.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for www.faphouse2.com.
Non-responsive IP for ftp.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain ftp.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for ftp.faphouse2.com.
Non-responsive IP for ftp.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain ftp.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for ftp.faphouse2.com.
Non-responsive IP for ns1.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain ns1.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for ns1.faphouse2.com.
Non-responsive IP for ns1.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain ns1.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for ns1.faphouse2.com.
Non-responsive IP for ns2.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain ns2.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for ns2.faphouse2.com.
Non-responsive IP for ns2.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain ns2.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for ns2.faphouse2.com.
Non-responsive IP for vpn.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain vpn.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for vpn.faphouse2.com.
Non-responsive IP for vpn.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain vpn.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for vpn.faphouse2.com.
Non-responsive IP for remote.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain remote.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for remote.faphouse2.com.
Non-responsive IP for remote.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain remote.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for remote.faphouse2.com.
Non-responsive IP for admin.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain admin.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for admin.faphouse2.com.
Non-responsive IP for admin.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain admin.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for admin.faphouse2.com.
Non-responsive IP for portal.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain portal.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for portal.faphouse2.com.
Non-responsive IP for portal.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain portal.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for portal.faphouse2.com.
Non-responsive IP for dev.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain dev.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for dev.faphouse2.com.
Non-responsive IP for dev.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain dev.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for dev.faphouse2.com.
Non-responsive IP for staging.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain staging.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for staging.faphouse2.com.
Non-responsive IP for staging.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain staging.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for staging.faphouse2.com.
Non-responsive IP for test.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain test.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for test.faphouse2.com.
Non-responsive IP for test.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain test.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for test.faphouse2.com.
Non-responsive IP for api.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain api.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for api.faphouse2.com.
Non-responsive IP for api.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain api.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for api.faphouse2.com.
Non-responsive IP for app.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain app.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for app.faphouse2.com.
Non-responsive IP for app.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain app.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for app.faphouse2.com.
Non-responsive IP for cdn.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain cdn.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for cdn.faphouse2.com.
Non-responsive IP for cdn.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain cdn.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for cdn.faphouse2.com.
Non-responsive IP for blog.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain blog.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for blog.faphouse2.com.
Non-responsive IP for blog.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain blog.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for blog.faphouse2.com.
Non-responsive IP for shop.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain shop.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for shop.faphouse2.com.
Non-responsive IP for shop.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain shop.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for shop.faphouse2.com.
Non-responsive IP for store.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain store.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for store.faphouse2.com.
Non-responsive IP for store.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain store.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for store.faphouse2.com.
Non-responsive IP for support.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain support.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for support.faphouse2.com.
Non-responsive IP for support.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain support.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for support.faphouse2.com.
Non-responsive IP for help.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain help.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for help.faphouse2.com.
Non-responsive IP for help.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain help.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for help.faphouse2.com.
Non-responsive IP for docs.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain docs.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for docs.faphouse2.com.
Non-responsive IP for docs.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain docs.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for docs.faphouse2.com.
Non-responsive IP for status.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain status.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for status.faphouse2.com.
Non-responsive IP for status.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain status.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for status.faphouse2.com.
Non-responsive IP for git.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain git.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for git.faphouse2.com.
Non-responsive IP for git.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain git.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for git.faphouse2.com.
Non-responsive IP for ci.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain ci.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for ci.faphouse2.com.
Non-responsive IP for ci.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain ci.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for ci.faphouse2.com.
Non-responsive IP for jenkins.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain jenkins.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for jenkins.faphouse2.com.
Non-responsive IP for jenkins.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain jenkins.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for jenkins.faphouse2.com.
Non-responsive IP for grafana.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain grafana.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for grafana.faphouse2.com.
Non-responsive IP for grafana.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain grafana.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for grafana.faphouse2.com.
Non-responsive IP for prometheus.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain prometheus.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for prometheus.faphouse2.com.
Non-responsive IP for prometheus.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain prometheus.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for prometheus.faphouse2.com.
Non-responsive IP for kibana.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain kibana.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for kibana.faphouse2.com.
Non-responsive IP for kibana.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain kibana.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for kibana.faphouse2.com.
Non-responsive IP for elastic.faphouse2.com: 2606:4700:3036::6815:3bf3
The subdomain elastic.faphouse2.com resolves to 2606:4700:3036::6815:3bf3 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3036::6815:3bf3 is operational or remove the DNS record for elastic.faphouse2.com.
Non-responsive IP for elastic.faphouse2.com: 2606:4700:3037::ac43:b9d4
The subdomain elastic.faphouse2.com resolves to 2606:4700:3037::ac43:b9d4 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:3037::ac43:b9d4 is operational or remove the DNS record for elastic.faphouse2.com.
Non-mail domain has no SPF record
This domain has no MX records (does not receive mail) but also has no SPF record. Without "v=spf1 -all", attackers can spoof this domain in phishing emails.
💡 Publish "v=spf1 -all" to explicitly declare this domain sends no mail.
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.
No MX records — A-record fallback active
The domain has no MX records but has an A record. Per RFC 5321, mail servers will attempt delivery to the A record IP. This domain may be silently accepting mail without SPF/DKIM/DMARC protection.
💡 If this domain should not receive mail, publish a Null MX record (RFC 7505): "0 ." as the MX. If it should receive mail, add proper MX records.
Domain enumerability: low
The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.
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 faphouse2.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 faphouse2.com and its subdomains. Each certificate reveals subdomain names.
Wildcard DNS record detected
A wildcard DNS record exists for *.faphouse2.com, resolving to 172.67.185.212, 104.21.59.243. Wildcard records make subdomain brute-forcing less effective but may mask misconfigurations.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.faphouse2.com is active and requires authentication.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain faphouse2.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 webmail.faphouse2.com
The Strict-Transport-Security header is not set on https://webmail.faphouse2.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
HSTS enabled but missing preload directive on faphouse2.com
Strict-Transport-Security: max-age=31536000; includeSubDomains
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
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://faphouse2.com/.well-known/security.txt.
TLS certificate valid for 49 days
Certificate for faphouse2.com expires on 2026-07-16.
Certificate issued by WE1
The certificate for faphouse2.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for faphouse2.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for faphouse2.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for faphouse2.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on faphouse2.com.
Domain valid for 297 days
Domain faphouse2.com expires on 2027-03-21.
No disposable email provider MX records
MX records for faphouse2.com do not match known disposable email provider patterns.
Domain is 797 days old
Domain faphouse2.com was registered 2024-03-21.
No wildcard MX records
No wildcard MX records detected for faphouse2.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
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.
No abuse contacts resolved
Could not resolve abuse contact information for MX IPs via abusix.org.
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: Name.com, Inc. | Created: 2024-03-21 | Expires: 2027-03-21 | Updated: 2026-01-13
WHOIS privacy protection enabled
Domain faphouse2.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: faphouse.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 missing
→
DMARC Policy
DMARC policy missing
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
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.
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
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
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/faphouse2.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan faphouse2.com Again