SurfaceMap › p › proxiserve.fr

proxiserve.fr

Checked 2026-10-22 04:54 UTC · first added 2026-10-21
✗Problems found Score 72 of 100

Domain & DNS

fail

23 passed 2 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns3.iptwins.com (144.217.70.141): read tcp 46.225.38.91:36308->144.217.70.141:53: i/o timeout; ns3.iptwins.com (2607:5300:203:28d::): read tcp [2a01:4f8:1c1c:eebf::1]:45908->[2607:5300:203:28d::]:53: i/o timeout.
    #19
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 4d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 2h, expire 30d, negative TTL 4d.
    #23
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

✗

Full report

Domain & DNS report for proxiserve.fr ›

Mail

warn

25 passed 4 warn 0 failed

Areas

✓SPF !DMARC !DKIM !DNSSEC ✓MX !TLS iBIMI

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

!

Full report

Mail report for proxiserve.fr ›