Check DNS, Urls + Redirects, Certificates and Content of your Website

0 in Queue, 0 of max. 8 Checks (17:18:42)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

T

 

Timeout

 

Checked:
09.06.2025 21:07:18

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
jesper.wiki
A
87.208.118.99
Tiel/Gelderland/The Netherlands (NL) - T-Mobile Thuis WBA Services
Hostname: 99-118-208-87.ftth.glasoperator.nl
yes
1
0

AAAA

yes


www.jesper.wiki
A
87.208.118.99
Tiel/Gelderland/The Netherlands (NL) - T-Mobile Thuis WBA Services
Hostname: 99-118-208-87.ftth.glasoperator.nl
yes
1
0

AAAA

yes


*.jesper.wiki
A
87.208.118.99
yes



AAAA

yes



CNAME

yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=






• Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 38696, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 53148, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.06.2025, 00:00:00 +, Signature-Inception: 31.05.2025, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: wiki

wiki
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 27157, DigestType 2 and Digest xyR4pJhqUzD7IaLkJ4I1UxMdcMOZ3bz+3uOVEDyoVD0=






1 RRSIG RR to validate DS RR found






RRSIG-Owner wiki., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.06.2025, 17:00:00 +, Signature-Inception: 09.06.2025, 16:00:00 +, KeyTag 53148, Signer-Name: (root)






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 53148 used to validate the DS RRSet in the parent zone






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 27157, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 57159, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner wiki., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 18.06.2025, 20:15:40 +, Signature-Inception: 04.06.2025, 20:04:18 +, KeyTag 27157, Signer-Name: wiki






• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 27157 used to validate the DNSKEY RRSet






• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 27157, DigestType 2 and Digest "xyR4pJhqUzD7IaLkJ4I1UxMdcMOZ3bz+3uOVEDyoVD0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: jesper.wiki

jesper.wiki
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "1s4dppe4aaesi470u1ageg5ufbdjpm8f" between the hashed NSEC3-owner "1s10cs8jfugkelllab8709qvglpd49gv" and the hashed NextOwner "1s9seki5dbmhq256cqbmouvto0inr7og". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 1s10cs8jfugkelllab8709qvglpd49gv.wiki., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 22.06.2025, 02:08:11 +, Signature-Inception: 09.06.2025, 15:04:35 +, KeyTag 57159, Signer-Name: wiki






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "73m6trb7qde3nv4vuh40n34j73ja22vo" as Owner. That's the Hash of "wiki" with the NextHashedOwnerName "73pqcm3f80eq3998sd3ig0b7il8ppqg7". So that domain name is the Closest Encloser of "jesper.wiki". Opt-Out: True.
Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner 73m6trb7qde3nv4vuh40n34j73ja22vo.wiki., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 19.06.2025, 21:42:07 +, Signature-Inception: 05.06.2025, 21:20:39 +, KeyTag 57159, Signer-Name: wiki






0 DNSKEY RR found









Zone: www.jesper.wiki

www.jesper.wiki
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.jesper.wiki
•  dns1.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1
•
jesper.wiki
•  dns1.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1
156.154.132.200
Toronto/Ohio/United States (US) - Neustar Security Services		•

• 
2610:a1:1024::200
Herndon/Virginia/United States (US) - Vercara, LLC		•

•  dns2.registrar-servers.com / Auth_NC_Host1.Frankfurt_Node1
156.154.133.200
Toronto/Ohio/United States (US) - Neustar Security Services		•

• 
2610:a1:1025::200
Sterling/Virginia/United States (US) - Vercara, LLC		•
wiki
•  a.nic.wiki / dns4.defra1
•

•  b.nic.wiki / dns3.defra1
•

•  c.nic.wiki / dns3.defra1
•

•  x.nic.wiki / Auth_Host4.Frankfurt_Node1
•

•  y.nic.wiki / Auth_Host2.Frankfurt_Node1
•

•  z.nic.wiki / Auth_Host1.Frankfurt_Node1
•

 

4. SOA-Entries


Domain:wiki
Zone-Name:wiki
Primary:a.nic.wiki
Mail:admin.tldns.godaddy
Serial:1749495918
Refresh:1800
Retry:300
Expire:604800
TTL:1800
num Entries:6


Domain:jesper.wiki
Zone-Name:jesper.wiki
Primary:dns1.registrar-servers.com
Mail:hostmaster.registrar-servers.com
Serial:1749495872
Refresh:43200
Retry:3600
Expire:604800
TTL:3601
num Entries:4


Domain:www.jesper.wiki
Zone-Name:jesper.wiki
Primary:dns1.registrar-servers.com
Mail:hostmaster.registrar-servers.com
Serial:1749495872
Refresh:43200
Retry:3600
Expire:604800
TTL:3601
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

 

 

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://jesper.wiki/
87.208.118.99
-14


10.030
T
Timeout - The operation has timed out.

• http://www.jesper.wiki/
87.208.118.99
-14


10.023
T
Timeout - The operation has timed out.

• https://jesper.wiki/
87.208.118.99
-14


10.030
T
Timeout - The operation has timed out.

• https://www.jesper.wiki/
87.208.118.99
-14


10.027
T
Timeout - The operation has timed out.

• http://jesper.wiki/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
87.208.118.99
-14


10.026
T
Timeout - The operation has timed out.
Visible Content:

• http://www.jesper.wiki/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
87.208.118.99
-14


10.026
T
Timeout - The operation has timed out.
Visible Content:

• https://87.208.118.99/
87.208.118.99
-14


10.020
T
Timeout - The operation has timed out.

 

7. Comments


1. General Results, most used to calculate the result

Aname "jesper.wiki" is domain, public suffix is ".wiki", top-level-domain is ".wiki", top-level-domain-type is "generic", tld-manager is "Top Level Design, LLC", num .wiki-domains preloaded: 123 (complete: 271405)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: jesper.wiki has only one ip address.
Warning: Only one ip address found: www.jesper.wiki has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: jesper.wiki has no ipv6 address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.jesper.wiki has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain jesper.wiki, 1 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.jesper.wiki, 1 ip addresses.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.jesper.wiki

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 24 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 24 Queries complete, 23 with IPv6, 1 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Bad (greater 8):: An average of 12.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in Delegation: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in 1 Zone definitions: dns1.registrar-servers.com, dns2.registrar-servers.com, 1 Name Servers listed in SOA.Primary: dns1.registrar-servers.com.
AGood: Only one SOA.Primary Name Server found.: dns1.registrar-servers.com.
AGood: SOA.Primary Name Server included in the delegation set.: dns1.registrar-servers.com.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: dns1.registrar-servers.com, dns2.registrar-servers.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: registrar-servers.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 156., 1 different subnets (first two Bytes): 156.154., 2 different subnets (first three Bytes): 156.154.132., 156.154.133.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2610:, 1 different subnets (first two blocks): 2610:00a1:, 2 different subnets (first three blocks): 2610:00a1:1024:, 2610:00a1:1025:, 2 different subnets (first four blocks): 2610:00a1:1024:0000:, 2610:00a1:1025:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: c.nic.wiki: OP100: ok. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (dns3.defra1). COOKIE: ok. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

http://jesper.wiki/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 87.208.118.99
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.jesper.wiki/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 87.208.118.99
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 125204 milliseconds, 125.204 seconds

 

8. Connections

No connection informations found. Perhaps only http - connections.

 

9. Certificates

No certificate informations found. Perhaps only http - connections.

 

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found

 

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

No CRT - CT-Log entries found

 

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

 

12. Html-Parsing via https://validator.w3.org/nu/


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns1.registrar-servers.com, dns2.registrar-servers.com

 

QNr.DomainTypeNS used
1
com
NS
m.root-servers.net (2001:dc3::35)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
dns1.registrar-servers.com
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: edns1.registrar-servers.com, edns2.registrar-servers.com, edns3.registrar-servers.com, edns4.registrar-servers.com, edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org

Answer: edns1.registrar-servers.com
2001:41d0:800:2d2c::2, 51.89.217.44

Answer: edns2.registrar-servers.com
2607:5300:203:7f53::2, 51.222.46.83

Answer: edns3.registrar-servers.com
193.108.91.149, 2.16.130.65, 2600:1401:2::95, 2600:1480:9800::41, 2a02:26f0:67::43, 95.100.175.67

Answer: edns4.registrar-servers.com
2.22.230.67, 23.211.132.64, 2600:1406:1b::40, 2600:1408:1c::40, 2600:1480:800::43, 96.7.49.64

Answer: edns4.ultradns.com
2001:502:f3ff::204, 204.74.66.4
3
dns2.registrar-servers.com
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: edns1.registrar-servers.com, edns2.registrar-servers.com, edns3.registrar-servers.com, edns4.registrar-servers.com, edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org

Answer: edns1.registrar-servers.com
2001:41d0:800:2d2c::2, 51.89.217.44

Answer: edns2.registrar-servers.com
2607:5300:203:7f53::2, 51.222.46.83

Answer: edns3.registrar-servers.com
193.108.91.149, 2.16.130.65, 2600:1401:2::95, 2600:1480:9800::41, 2a02:26f0:67::43, 95.100.175.67

Answer: edns4.registrar-servers.com
2.22.230.67, 23.211.132.64, 2600:1406:1b::40, 2600:1408:1c::40, 2600:1480:800::43, 96.7.49.64

Answer: edns4.ultradns.com
2001:502:f3ff::204, 204.74.66.4
4
biz
NS
e.root-servers.net (2001:500:a8::e)

Answer: a.gtld.biz, b.gtld.biz, c.gtld.biz, m.gtld.biz, n.gtld.biz, w.gtld.biz, x.gtld.biz, y.gtld.biz
5
edns4.ultradns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org

Answer: pdns196.ultradns.biz
156.154.66.196, 2610:a1:1015::e8
6
net
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
7
edns4.ultradns.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns61.ultradns2.com, ns61.ultradns2.org, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org

Answer: pdns196.ultradns.net
156.154.65.196, 2610:a1:1014::e8
8
org
NS
d.root-servers.net (2001:500:2d::d)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
9
edns4.ultradns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns61.ultradns2.com, ns61.ultradns2.org, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org

Answer: ns61.ultradns2.org
204.74.106.61, 2610:a1:323d::53

Answer: pdns196.ultradns.org
156.154.67.196, 2001:502:4612::e8
10
uk
NS
b.root-servers.net (2001:500:200::b)

Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
11
pdns196.ultradns.co.uk: 156.154.69.196, 2610:a1:1017::e8
NS
dns1.nic.uk (2a01:618:400::1)
12
pdns196.ultradns.com: 156.154.64.196, 2001:502:f3ff::e8
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: ns61.ultradns2.com
204.74.104.61, 2610:a1:313d::53
13
info
NS
d.root-servers.net (199.7.91.13)

Answer: a0.info.afilias-nst.info, a2.info.afilias-nst.info, b0.info.afilias-nst.org, b2.info.afilias-nst.org, c0.info.afilias-nst.info, d0.info.afilias-nst.org
14
pdns196.ultradns.info: 156.154.68.196, 2610:a1:1016::e8
NS
a0.info.afilias-nst.info (2001:500:19::1)
15
edns4.ultradns.biz: 204.74.67.4
A
pdns196.ultradns.biz (2610:a1:1015::e8)
16
edns4.ultradns.biz: 2610:a1:1015::204
AAAA
pdns196.ultradns.biz (2610:a1:1015::e8)
17
edns4.ultradns.net: 204.74.110.4
A
ns61.ultradns2.com (2610:a1:313d::53)
18
edns4.ultradns.net: 2610:a1:1014::204
AAAA
ns61.ultradns2.com (2610:a1:313d::53)
19
edns4.ultradns.org: 204.74.111.4
A
ns61.ultradns2.com (2610:a1:313d::53)
20
edns4.ultradns.org: 2001:502:4612::204
AAAA
ns61.ultradns2.com (2610:a1:313d::53)
21
dns1.registrar-servers.com: 156.154.132.200
A
edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
22
dns1.registrar-servers.com: 2610:a1:1024::200
AAAA
edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
23
dns2.registrar-servers.com: 156.154.133.200
A
edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
24
dns2.registrar-servers.com: 2610:a1:1025::200
AAAA
edns1.registrar-servers.com (2001:41d0:800:2d2c::2)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.jesper.wiki
0

no CAA entry found
1
0
jesper.wiki
0

no CAA entry found
1
0
wiki
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
jesper.wiki
v=spf1 include:spf.efwd.registrar-servers.com ~all
ok
1
0
www.jesper.wiki

ok
1
0
_acme-challenge.jesper.wiki

missing entry or wrong length
1
0
_acme-challenge.www.jesper.wiki

missing entry or wrong length
1
0
_acme-challenge.jesper.wiki.jesper.wiki

 perhaps wrong
1
0
_acme-challenge.www.jesper.wiki.jesper.wiki

 perhaps wrong
1
0
_acme-challenge.www.jesper.wiki.www.jesper.wiki

 perhaps wrong
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

jesper.wiki
10
eforward1.registrar-servers.com
05ok

A


162.255.118.51
01ok

CNAME


00ok
MX

jesper.wiki
10
eforward2.registrar-servers.com
05ok

A


162.255.118.52
01ok

CNAME


00ok
MX

jesper.wiki
10
eforward3.registrar-servers.com
05ok

A


162.255.118.51
01ok

CNAME


00ok
MX

jesper.wiki
15
eforward4.registrar-servers.com
05ok

A


162.255.118.52
01ok

CNAME


00ok
MX

jesper.wiki
20
eforward5.registrar-servers.com
05ok

A


162.255.118.51
01ok

CNAME


00ok
SPF
TXT
jesper.wiki

v=spf1 include:spf.efwd.registrar-servers.com ~all
ok

TXT
spf.efwd.registrar-servers.com

v=spf1 ip4:209.105.246.192/28 ip4:198.54.122.192/26 ip4:162.255.118.0/26 ip4:198.54.122.0/28 ip4:162.255.118.240/29 ip4:63.250.43.96/27 ip4:198.177.126.16/28 ?all
ok

				 
			

				 
			
17. Cipher Suites
No results 

				 
			
18. Portchecks



No open Ports <> 80 / 443 found, so no additional Ports checked.



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=5be496f4-399c-4f46-9775-95023869207b

				 
			


Last Result: https://check-your-website.server-daten.de/?q=jesper.wiki - 2025-06-09 21:07:18

				 
			
Do you like this page? Support this tool, add a link on your page:

				 
			
<a href="https://check-your-website.server-daten.de/?q=jesper.wiki" target="_blank">Check this Site: jesper.wiki</a>

				 
			

				 
			


Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

				 
			
QR-Code of this page - https://check-your-website.server-daten.de/?d=jesper.wiki

				 
			

				 
			



Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • 
USt-IdNr.: DE221734518

				 
			


Errors, ideas, questions? Use the 
Contact form • A project using

Server-Daten - Web Database solutions