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



T

Timeout

Checked:
16.09.2020 06:38:31


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
cloud.informabox.tech
A
92.148.203.126
Strasbourg/Grand Est/France (FR) - France Telecom Orange
Hostname: lfbn-str-1-716-126.w92-148.abo.wanadoo.fr
yes
1
0

AAAA

yes


www.cloud.informabox.tech
A
92.148.203.126
Strasbourg/Grand Est/France (FR) - France Telecom Orange
Hostname: lfbn-str-1-716-126.w92-148.abo.wanadoo.fr
yes
1
0

AAAA

yes


*.informabox.tech
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.cloud.informabox.tech
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: tech
tech
2 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 50095, DigestType 1 and Digest gvcvJGLe4luZ2iRwU1rQp9Ex8es=



DS with Algorithm 8, KeyTag 50095, DigestType 2 and Digest g/QNARQUhNjwcwXl0uRKxWYxSQVMWY1unZk8ZhaGxu4=



1 RRSIG RR to validate DS RR found



RRSIG-Owner tech., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.09.2020, 21:00:00 +, Signature-Inception: 15.09.2020, 20: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 3864, Flags 256



Public Key with Algorithm 8, KeyTag 20124, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner tech., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 01.10.2020, 07:28:54 +, Signature-Inception: 01.09.2020, 13:09:29 +, KeyTag 50095, Signer-Name: tech



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



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



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

Zone: informabox.tech
informabox.tech
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 "2i49j57gql59pjngtsrpqjvin4sp1bpg" between the hashed NSEC3-owner "2hvhhgtfbu2f825kc5d0q1dhq52aiotj" and the hashed NextOwner "2i7inhjmcirgar3su8884t8uekt6poac". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 2hvhhgtfbu2f825kc5d0q1dhq52aiotj.tech., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 05.10.2020, 23:28:19 +, Signature-Inception: 06.09.2020, 07:14:38 +, KeyTag 3864, Signer-Name: tech



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "9btf69hmd3n6368rdfnvtq09vgqbb2th" as Owner. That's the Hash of "tech" with the NextHashedOwnerName "9c1pdns5c56jok2dks51nvl42k1tl8gp". So that domain name is the Closest Encloser of "informabox.tech". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 9btf69hmd3n6368rdfnvtq09vgqbb2th.tech., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 15.10.2020, 11:26:57 +, Signature-Inception: 15.09.2020, 10:31:58 +, KeyTag 3864, Signer-Name: tech



0 DNSKEY RR found




Zone: cloud.informabox.tech
cloud.informabox.tech
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.cloud.informabox.tech
www.cloud.informabox.tech
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.cloud.informabox.tech
  dns111.ovh.net

cloud.informabox.tech
  dns111.ovh.net
213.251.188.155
Roubaix/Hauts-de-France/France (FR) - OVH ISP


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

informabox.tech
  dns111.ovh.net
213.251.188.155
Roubaix/Hauts-de-France/France (FR) - OVH ISP


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


  ns111.ovh.net
213.251.128.155
Roubaix/Hauts-de-France/France (FR) - OVH ISP


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

tech
  a.nic.tech / CEQY-QU41GH-6UZLZF


  b.nic.tech / CKQV-6AF162-DWW7G4


  e.nic.tech / BTWZ-5DPYTA-R2KDLV


  f.nic.tech / YPGW-ROF3HM-2JNKNU


  ns0.centralnic.net


4. SOA-Entries


Domain:tech
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:tech
Zone-Name:tech
Primary:ns0.centralnic.net
Mail:hostmaster.centralnic.net
Serial:277650
Refresh:900
Retry:1800
Expire:6048000
TTL:3600
num Entries:4


Domain:informabox.tech
Zone-Name:informabox.tech
Primary:dns111.ovh.net
Mail:tech.ovh.net
Serial:2020090906
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:4


Domain:cloud.informabox.tech
Zone-Name:informabox.tech
Primary:dns111.ovh.net
Mail:tech.ovh.net
Serial:2020090906
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:2


Domain:www.cloud.informabox.tech
Zone-Name:informabox.tech
Primary:dns111.ovh.net
Mail:tech.ovh.net
Serial:2020090906
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
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://cloud.informabox.tech/
92.148.203.126 No GZip used - 499 / 612 - 81.54 % possible
200

Html is minified: 129.94 %
0.043
H
small visible content (num chars: 273)
Welcome to nginx! If you see this page, the nginx web server is successfully installed and working. Further configuration is required. For online documentation and support please refer to nginx.org . Commercial support is available at nginx.com . Thank you for using nginx.
Server: nginx/1.19.2
Date: Wed, 16 Sep 2020 04:39:02 GMT
Content-Type: text/html
Content-Length: 612
Last-Modified: Tue, 11 Aug 2020 14:52:34 GMT
Connection: close
ETag: "5f32b0b2-264"
Accept-Ranges: bytes

• http://www.cloud.informabox.tech/
92.148.203.126 No GZip used - 499 / 612 - 81.54 % possible
200

Html is minified: 129.94 %
0.047
H
small visible content (num chars: 273)
Welcome to nginx! If you see this page, the nginx web server is successfully installed and working. Further configuration is required. For online documentation and support please refer to nginx.org . Commercial support is available at nginx.com . Thank you for using nginx.
Server: nginx/1.19.2
Date: Wed, 16 Sep 2020 04:39:02 GMT
Content-Type: text/html
Content-Length: 612
Last-Modified: Tue, 11 Aug 2020 14:52:34 GMT
Connection: close
ETag: "5f32b0b2-264"
Accept-Ranges: bytes

• https://cloud.informabox.tech/
92.148.203.126
-14

10.043
T
Timeout - The operation has timed out

• https://www.cloud.informabox.tech/
92.148.203.126
-14

10.013
T
Timeout - The operation has timed out

• http://cloud.informabox.tech/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
92.148.203.126
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.07 %
0.046
A
Not Found
Visible Content: 404 Not Found nginx/1.19.2
Server: nginx/1.19.2
Date: Wed, 16 Sep 2020 04:39:22 GMT
Content-Type: text/html
Content-Length: 153
Connection: close

• http://www.cloud.informabox.tech/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
92.148.203.126
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.07 %
0.060
A
Not Found
Visible Content: 404 Not Found nginx/1.19.2
Server: nginx/1.19.2
Date: Wed, 16 Sep 2020 04:39:22 GMT
Content-Type: text/html
Content-Length: 153
Connection: close

• https://92.148.203.126/
92.148.203.126
-14

10.026
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "cloud.informabox.tech" is subdomain, public suffix is ".tech", top-level-domain is ".tech", top-level-domain-type is "generic", tld-manager is "Dot Tech LLC", num .tech-domains preloaded: 273 (complete: 131120)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: cloud.informabox.tech has only one ip address.
Warning: Only one ip address found: www.cloud.informabox.tech 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: cloud.informabox.tech 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.cloud.informabox.tech has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (4 urls)
http://cloud.informabox.tech/ 92.148.203.126


Url with incomplete Content-Type - header - missing charset
http://www.cloud.informabox.tech/ 92.148.203.126


Url with incomplete Content-Type - header - missing charset
http://cloud.informabox.tech/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 92.148.203.126


Url with incomplete Content-Type - header - missing charset
http://www.cloud.informabox.tech/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 92.148.203.126


Url with incomplete Content-Type - header - missing charset
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Hfatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
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 cloud.informabox.tech, 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.cloud.informabox.tech, 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: dns111.ovh.net, ns111.ovh.net, 2 Name Servers included in Delegation: dns111.ovh.net, ns111.ovh.net, 2 Name Servers included in 1 Zone definitions: dns111.ovh.net, ns111.ovh.net, 1 Name Servers listed in SOA.Primary: dns111.ovh.net.
AGood: Only one SOA.Primary Name Server found.: dns111.ovh.net.
AGood: SOA.Primary Name Server included in the delegation set.: dns111.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: dns111.ovh.net, ns111.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:199b:, 2001:41d0:0001:4a9b:
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: f.nic.tech: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (YPGW-ROF3HM-2JNKNU). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns0.centralnic.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

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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: 83437 milliseconds, 83.437 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

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. Nameserver - IP-Adresses

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

QNr.DomainTypeNS used
1
net
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
dns111.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
ns111.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
dns111.ovh.net: 213.251.188.155
A
dns10.ovh.net (2001:41d0:1:4a81::1)
14
dns111.ovh.net: 2001:41d0:1:4a9b::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
15
ns111.ovh.net: 213.251.128.155
A
dns10.ovh.net (2001:41d0:1:4a81::1)
16
ns111.ovh.net: 2001:41d0:1:199b::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.cloud.informabox.tech
0

no CAA entry found
1
0
cloud.informabox.tech
0

no CAA entry found
1
0
informabox.tech
0

no CAA entry found
1
0
tech
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
informabox.tech
1|www.informabox.tech
ok
1
0
informabox.tech
v=spf1 include:mx.ovh.com ~all
ok
1
0
cloud.informabox.tech

ok
1
0
www.cloud.informabox.tech

ok
1
0
_acme-challenge.cloud.informabox.tech

Name Error - The domain name does not exist
1
0
_acme-challenge.www.cloud.informabox.tech

Name Error - The domain name does not exist
1
0
_acme-challenge.cloud.informabox.tech.informabox.tech

Name Error - The domain name does not exist
1
0
_acme-challenge.cloud.informabox.tech.cloud.informabox.tech

Name Error - The domain name does not exist
1
0
_acme-challenge.www.cloud.informabox.tech.cloud.informabox.tech

Name Error - The domain name does not exist
1
0
_acme-challenge.www.cloud.informabox.tech.www.cloud.informabox.tech

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=5ab8f7f5-ee19-450d-9f29-4fde7c2bf790


Last Result: https://check-your-website.server-daten.de/?q=cloud.informabox.tech - 2020-09-16 06:38:31


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

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