wifeo.com

Checked 22 October 2026, 11:31 UTC · via 8.8.8.8
✗Problems found
21 passed 3 warnings 3 failed 4 info

Registration

info

.com generic · Scaleway SAS · expires 2032-08-19

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Scaleway SAS
Registered
19 August 2005
Last changed
7 May 2026
Expires
19 August 2032
Status
client transfer prohibited
Registry nameservers
ns1.wifeo.com, ns2.sivit.org
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2032-08-19 #3
    The registration is valid until 2032-08-19 (2128 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.wifeo.com, ns2.sivit.org

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.wifeo.com, ns2.sivit.org
NS in the zone
ns1.wifeo.com, ns2.sivit.org
NameserverAddressesNetwork (AS)Glue
ns1.wifeo.com194.146.225.153AS13193 ASN-NERIM - Keyyo SA, FR194.146.225.153
ns2.sivit.org213.44.8.234AS5410 BOUYGTEL-ISP - Bouygues Telecom SA, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.wifeo.com, ns2.sivit.org.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.wifeo.com.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS13193 (ASN-NERIM - Keyyo SA, FR): 1 address; AS5410 (BOUYGTEL-ISP - Bouygues Telecom SA, FR): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .org.
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

1 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.wifeo.com 194.146.225.153NOERROR, 20 ms, authoritativenoyes / yesALLOWED (10 records)9.9.5-9+deb8u19-Debian
ns2.sivit.org 213.44.8.234REFUSED, 17 ms, NOT authoritativenono / yesrefusedPowerDNS Authoritative Server 4.5.3

Checks

  • ✓ All respond #14
    All 2 nameserver addresses answered.
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns2.sivit.org (213.44.8.234): REFUSED, authoritative=false.
    #15
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.wifeo.com: "9.9.5-9+deb8u19-Debian"; ns2.sivit.org: "PowerDNS Authoritative Server 4.5.3". Hide or replace the version string.
    #17
  • ✗
    Zone transfer allowed
    These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.wifeo.com (194.146.225.153): 10 records. Restrict zone transfers to your secondary servers.
    #18
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns2.sivit.org (213.44.8.234): .
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2005111003 · primary ns1.wifeo.com

Found

Primary (MNAME)
ns1.wifeo.com
Contact (RNAME)
tech.wifeo.com
Serial
2005111003
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Checks

  • ✓ Serial 2005111003 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.wifeo.com is one of the listed nameservers.
  • ✓ Contact tech@wifeo.com #25
    The SOA RNAME tech.wifeo.com means tech@wifeo.com.
  • ✓ Date-based serial #26
    The serial 2005111003 follows the YYYYMMDDnn convention (2005-11-10).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

info

5 records at the apex

Found

Read from
194.146.225.153:53
TypeValueTTL
SOAns1.wifeo.com. tech.wifeo.com. 2005111003 10800 3600 604800 360086400
NSns1.wifeo.com.86400
NSns2.sivit.org.86400
A194.146.225.15386400
MX10 mail.wifeo.com.86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, MX 1d, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35