SurfaceMap › t › telethon.fr

telethon.fr

Checked 2026-10-22 05:24 UTC · first added 2026-10-21
✗Problems found Score 49 of 100

Domain & DNS

fail

22 passed 3 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns1.perf1.com (81.92.94.100): REFUSED, authoritative=false; ns1.perf1.com (2a01:c8:100::100): REFUSED, authoritative=false; ns2.perf1.fr (81.92.95.100): REFUSED, authoritative=false; ns2.perf1.fr (2a01:c8:101::100): REFUSED, authoritative=false; ns3.perf1.eu (152.89.172.100): REFUSED, authoritative=false; ns3.perf1.eu (2a09:35c0:102::100): REFUSED, authoritative=false; ns4.perf1.de (81.92.94.100): REFUSED, authoritative=false; ns4.perf1.de (2a01:c8:100::100): REFUSED, authoritative=false; ns5.perf1.asia (81.92.95.100): REFUSED, authoritative=false; ns5.perf1.asia (2a01:c8:101::100): REFUSED, authoritative=false.
    #15
  • ✗
    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: ns1.perf1.com (81.92.94.100): ; ns1.perf1.com (2a01:c8:100::100): ; ns2.perf1.fr (81.92.95.100): ; ns2.perf1.fr (2a01:c8:101::100): ; ns3.perf1.eu (152.89.172.100): ; ns3.perf1.eu (2a09:35c0:102::100): ; ns4.perf1.de (81.92.94.100): ; ns4.perf1.de (2a01:c8:100::100): ; ns5.perf1.asia (81.92.95.100): ; ns5.perf1.asia (2a01:c8:101::100): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns0.clara.net, ns0.claranet.com, ns1.clara.net, ns1.claranet.com, ns2.clara.net, ns2.claranet.com; only in the zone: ns0.fr.claradns.net, ns1.fr.claradns.net, ns1.perf1.com, ns2.fr.claradns.net, ns2.perf1.fr, ns3.perf1.eu, ns4.perf1.de, ns5.perf1.asia. ns0.clara.net, ns0.claranet.com, ns0.fr.claradns.net, ns1.clara.net, ns1.claranet.com, ns1.fr.claradns.net, ns2.clara.net, ns2.claranet.com, ns2.fr.claradns.net report NS ns0.fr.claradns.net ns1.fr.claradns.net ns1.perf1.com ns2.fr.claradns.net ns2.perf1.fr ns3.perf1.eu ns4.perf1.de ns5.perf1.asia.
    #7
  • !
    Unusual SOA timers
    SOA · refresh 2d is outside 20m–1d; negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 2d, retry 1h, expire 20d, negative TTL 2d.
    #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 telethon.fr ›

Mail

fail

16 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    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 telethon.fr ›