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



Y

Private IP-Address found

Checked:
15.09.2020 23:49:50


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mail.ianfd.de
A
194.62.6.34
Amsterdam/North Holland/Netherlands (NL) - Marcel Andrew Zaiser trading as Metaliance ISP Systems e.k
No Hostname found
yes
1
0

AAAA
fe80::d466:b4ff:fe35:7fc9

yes


www.mail.ianfd.de

Name Error
yes
1
0
*.ianfd.de
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.mail.ianfd.de
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 46594, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2020, 00:00:00 +, Signature-Inception: 09.09.2020, 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: de
de
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 45580, DigestType 2 and Digest kYwy4vEiEXZr5iJmdPRHRY8iWbmg2HtE0p1Vr+ymsuE=



1 RRSIG RR to validate DS RR found



RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.09.2020, 17:00:00 +, Signature-Inception: 15.09.2020, 16:00:00 +, KeyTag 46594, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 30900, Flags 256



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



Public Key with Algorithm 8, KeyTag 64263, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 28.09.2020, 15:50:06 +, Signature-Inception: 14.09.2020, 14:20:06 +, KeyTag 45580, Signer-Name: de



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



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

Zone: ianfd.de
ianfd.de
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 64585, DigestType 2 and Digest Xl+kdS0XK/38LIhc5W6I8jJT13lw/R76tuya0RwSZRY=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ianfd.de., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 24.09.2020, 08:02:01 +, Signature-Inception: 10.09.2020, 06:32:01 +, KeyTag 64263, Signer-Name: de



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 58689, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ianfd.de., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



RRSIG-Owner ianfd.de., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 64585, Signer-Name: ianfd.de



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 64585, DigestType 2 and Digest "Xl+kdS0XK/38LIhc5W6I8jJT13lw/R76tuya0RwSZRY=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: mail.ianfd.de
mail.ianfd.de
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 "o3qffth9ckjpn7vi8lhtfdih81uhk7g8" between the hashed NSEC3-owner "o3qffth9ckjpn7vi8lhtfdih81uhk7g8" and the hashed NextOwner "pj7p09d2pbhv9lfoj0t7pcbf9f4fsfqi". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, MX, AAAA, RRSIG Validated: RRSIG-Owner o3qffth9ckjpn7vi8lhtfdih81uhk7g8.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



0 DNSKEY RR found






RRSIG Type 1 validates the A - Result: 194.62.6.34
Validated: RRSIG-Owner mail.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



RRSIG Type 28 validates the AAAA - Result: FE80:0000:0000:0000:D466:B4FF:FE35:7FC9
Validated: RRSIG-Owner mail.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "o3qffth9ckjpn7vi8lhtfdih81uhk7g8" equal the hashed NSEC3-owner "o3qffth9ckjpn7vi8lhtfdih81uhk7g8" and the hashed NextOwner "pj7p09d2pbhv9lfoj0t7pcbf9f4fsfqi". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, MX, AAAA, RRSIG Validated: RRSIG-Owner o3qffth9ckjpn7vi8lhtfdih81uhk7g8.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed query name "o3qffth9ckjpn7vi8lhtfdih81uhk7g8" equal the hashed NSEC3-owner "o3qffth9ckjpn7vi8lhtfdih81uhk7g8" and the hashed NextOwner "pj7p09d2pbhv9lfoj0t7pcbf9f4fsfqi". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, MX, AAAA, RRSIG Validated: RRSIG-Owner o3qffth9ckjpn7vi8lhtfdih81uhk7g8.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.mail.ianfd.de) sends a valid NSEC3 RR as result with the hashed owner name "o3qffth9ckjpn7vi8lhtfdih81uhk7g8" (unhashed: mail.ianfd.de). So that's the Closest Encloser of the query name.
Bitmap: A, MX, AAAA, RRSIG Validated: RRSIG-Owner o3qffth9ckjpn7vi8lhtfdih81uhk7g8.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "nga231nhcag06doimdh0v9652pncnhrn" (unhashed: _tcp.mail.ianfd.de) with the owner "mhj0lpcviqlt8eb8roa54ostmut8cq7j" and the NextOwner "o3qffth9ckjpn7vi8lhtfdih81uhk7g8". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: TXT, RRSIG Validated: RRSIG-Owner mhj0lpcviqlt8eb8roa54ostmut8cq7j.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "83cf9ou74nl40fnbjc6mqpcqbh8qpfrb" (unhashed: *.mail.ianfd.de) with the owner "6s1k7ch7opvvpjsogo70ddort5rags48" and the NextOwner "b2k808pplrpfdcqgigdjlmrn0d4nb8qm". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: A, MX, TXT, RRSIG Validated: RRSIG-Owner 6s1k7ch7opvvpjsogo70ddort5rags48.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "o3qffth9ckjpn7vi8lhtfdih81uhk7g8" equal the hashed NSEC3-owner "o3qffth9ckjpn7vi8lhtfdih81uhk7g8" and the hashed NextOwner "pj7p09d2pbhv9lfoj0t7pcbf9f4fsfqi". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, MX, AAAA, RRSIG Validated: RRSIG-Owner o3qffth9ckjpn7vi8lhtfdih81uhk7g8.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



Status: Good. NoData-Proof required and found.

Zone: www.mail.ianfd.de
www.mail.ianfd.de
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 "hfeffdlbpgic0lctj34721pfpn0h7du8" between the hashed NSEC3-owner "hefsdm53ji3mq27rqspp752323a8aig2" and the hashed NextOwner "iejpq2cnacn9b9bf4k658li1ufnfofl0". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner hefsdm53ji3mq27rqspp752323a8aig2.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "o3qffth9ckjpn7vi8lhtfdih81uhk7g8" as Owner. That's the Hash of "mail.ianfd.de" with the NextHashedOwnerName "pj7p09d2pbhv9lfoj0t7pcbf9f4fsfqi". So that domain name is the Closest Encloser of "www.mail.ianfd.de". Opt-Out: False.
Bitmap: A, MX, AAAA, RRSIG Validated: RRSIG-Owner o3qffth9ckjpn7vi8lhtfdih81uhk7g8.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de



The ClosestEncloser says, that "*.mail.ianfd.de" with the Hash "83cf9ou74nl40fnbjc6mqpcqbh8qpfrb" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "6s1k7ch7opvvpjsogo70ddort5rags48" and the Next Owner "b2k808pplrpfdcqgigdjlmrn0d4nb8qm", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: A, MX, TXT, RRSIG Validated: RRSIG-Owner 6s1k7ch7opvvpjsogo70ddort5rags48.ianfd.de., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 15.10.2020, 20:45:34 +, Signature-Inception: 15.09.2020, 20:45:34 +, KeyTag 58689, Signer-Name: ianfd.de


3. Name Servers

DomainNameserverNS-IP
www.mail.ianfd.de
  dns107.ovh.net

mail.ianfd.de
  dns107.ovh.net
213.251.188.151
Roubaix/Hauts-de-France/France (FR) - OVH ISP


 
2001:41d0:1:4a97::1
Bouxieres-aux-Dames/Grand Est/France (FR) - OVH SAS

ianfd.de
  dns107.ovh.net
213.251.188.151
Roubaix/Hauts-de-France/France (FR) - OVH ISP


 
2001:41d0:1:4a97::1
Bouxieres-aux-Dames/Grand Est/France (FR) - OVH SAS


  ns107.ovh.net
213.251.128.151
Roubaix/Hauts-de-France/France (FR) - OVH ISP


 
2001:41d0:1:1997::1
Bouxieres-aux-Dames/Grand Est/France (FR) - OVH SAS

de
  a.nic.de / ns-2.de.de8.bind


  f.nic.de / ns-1.de.de1


  l.de.net / ns-1.de.fr1


  n.de.net / s3.amx


  s.de.net / ns-3.de.de9


  z.nic.de / ns-3.de.de2.bind


4. SOA-Entries


Domain:de
Zone-Name:de
Primary:f.nic.de
Mail:its.denic.de
Serial:1600206474
Refresh:7200
Retry:7200
Expire:3600000
TTL:7200
num Entries:6


Domain:ianfd.de
Zone-Name:ianfd.de
Primary:dns107.ovh.net
Mail:tech.ovh.net
Serial:2020091510
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:4


Domain:mail.ianfd.de
Zone-Name:ianfd.de
Primary:dns107.ovh.net
Mail:tech.ovh.net
Serial:2020091510
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:2


Domain:www.mail.ianfd.de
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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://mail.ianfd.de/
194.62.6.34
-14

10.014
T
Timeout - The operation has timed out

• https://mail.ianfd.de/
194.62.6.34
-14

10.014
T
Timeout - The operation has timed out

• http://mail.ianfd.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
194.62.6.34
-14

10.030
T
Timeout - The operation has timed out
Visible Content:

• https://194.62.6.34/
194.62.6.34
-14

10.030
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "mail.ianfd.de" is subdomain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 6338 (complete: 131120)
Warning: Only one ip address found: mail.ianfd.de 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: mail.ianfd.de has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Ymail.ianfd.de

fe80::d466:b4ff:fe35:7fc9
Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check https://en.wikipedia.org/wiki/Private_network to understand the details: fe80:0000:0000:0000:0000:0000:0000:0000 to fe80:ffff:ffff:ffff:ffff:ffff:ffff:ffff: Link-local address
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 mail.ianfd.de, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 8.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns107.ovh.net, ns107.ovh.net, 2 Name Servers included in Delegation: dns107.ovh.net, ns107.ovh.net, 2 Name Servers included in 1 Zone definitions: dns107.ovh.net, ns107.ovh.net, 1 Name Servers listed in SOA.Primary: dns107.ovh.net.
AGood: Only one SOA.Primary Name Server found.: dns107.ovh.net.
AGood: SOA.Primary Name Server included in the delegation set.: dns107.ovh.net.
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: dns107.ovh.net, ns107.ovh.net
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: net
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: ovh.net
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: FR
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 213., 1 different subnets (first two Bytes): 213.251., 2 different subnets (first three Bytes): 213.251.128., 213.251.188.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:41d0:, 1 different subnets (first three blocks): 2001:41d0:0001:, 2 different subnets (first four blocks): 2001:41d0:0001:1997:, 2001:41d0:0001:4a97:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: dns107.ovh.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
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.

3. Content- and Performance-critical Checks

http://mail.ianfd.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 194.62.6.34
-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: 88687 milliseconds, 88.687 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" > 2019 are listed

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3355113671
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-08 11:09:19
2020-12-07 12:09:19
*.ianfd.de, ianfd.de
2 entries



11. Html-Content - Entries

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


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns107.ovh.net, ns107.ovh.net

QNr.DomainTypeNS used
1
net
NS
l.root-servers.net (2001:500:9f::42)

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
dns107.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
213.251.128.131
3
ns107.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
213.251.128.131
4
dns13.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
5
ns13.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
6
ns15.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
7
dns13.ovh.net: 213.251.188.132
A
dns10.ovh.net (2001:41d0:1:4a81::1)
8
dns13.ovh.net: 2001:41d0:1:4a84::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
9
ns13.ovh.net: 213.251.128.132
A
dns10.ovh.net (2001:41d0:1:4a81::1)
10
ns13.ovh.net: 2001:41d0:1:1984::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
11
ns15.ovh.net: 213.251.128.134
A
dns10.ovh.net (2001:41d0:1:4a81::1)
12
ns15.ovh.net: 2001:41d0:1:1986::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
13
dns107.ovh.net: 213.251.188.151
A
dns10.ovh.net (2001:41d0:1:4a81::1)
14
dns107.ovh.net: 2001:41d0:1:4a97::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
15
ns107.ovh.net: 213.251.128.151
A
dns10.ovh.net (2001:41d0:1:4a81::1)
16
ns107.ovh.net: 2001:41d0:1:1997::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
mail.ianfd.de
0

no CAA entry found
1
0
ianfd.de
0

no CAA entry found
1
0
de
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
ianfd.de
1|www.ianfd.de
ok
1
0
ianfd.de
v=spf1 include:mx.ovh.com ~all
ok
1
0
mail.ianfd.de

ok
1
0
_acme-challenge.mail.ianfd.de

Name Error - The domain name does not exist
1
0
_acme-challenge.mail.ianfd.de.ianfd.de

Name Error - The domain name does not exist
1
0
_acme-challenge.mail.ianfd.de.mail.ianfd.de

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=731e4c70-7cd3-4be3-8569-65af36256c16


Last Result: https://check-your-website.server-daten.de/?q=mail.ianfd.de - 2020-09-15 23:49:50


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

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