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




X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
12.02.2024 13:43:51


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
miao.bounceme.net
A
34.199.8.144
Ashburn/Virginia/United States (US) - Amazon.com, Inc.
Hostname: ec2-34-199-8-144.compute-1.amazonaws.com
yes
1
0

AAAA

yes


www.miao.bounceme.net

Name Error
yes
1
0
*.miao.bounceme.net
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 30903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=



1 RRSIG RR to validate DS RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.02.2024, 05:00:00 +, Signature-Inception: 12.02.2024, 04:00:00 +, KeyTag 30903, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 34730, Flags 256



Public Key with Algorithm 13, KeyTag 37331, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.02.2024, 15:10:35 +, Signature-Inception: 07.02.2024, 15:05:35 +, KeyTag 37331, Signer-Name: net



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 37331 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: bounceme.net
bounceme.net
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 "jfdsvb1hcf22qh01d7inp8fklgcaci9l" between the hashed NSEC3-owner "jfdspsa3toorics42jss0nr2i625jeee" and the hashed NextOwner "jfdsvgndj8ona42vbbs3p1t1lf64hnkk". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner jfdspsa3toorics42jss0nr2i625jeee.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 17.02.2024, 08:25:36 +, Signature-Inception: 10.02.2024, 07:15:36 +, KeyTag 34730, Signer-Name: net



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "bounceme.net". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 18.02.2024, 08:21:03 +, Signature-Inception: 11.02.2024, 07:11:03 +, KeyTag 34730, Signer-Name: net



0 DNSKEY RR found




Zone: miao.bounceme.net
miao.bounceme.net
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.miao.bounceme.net
www.miao.bounceme.net
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.miao.bounceme.net
  nf1.no-ip.com

miao.bounceme.net
  nf1.no-ip.com / F0202-FRA-HV
194.62.182.53
Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC


 
2a07:dc00:1820::53
New York/United States (US) - Vitalwerks Internet Solutions, LLC

bounceme.net
  nf1.no-ip.com / F0202-FRA-HV
194.62.182.53
Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC


 
2a07:dc00:1820::53
New York/United States (US) - Vitalwerks Internet Solutions, LLC


  nf2.no-ip.com / F0201-FRA-HV
45.54.64.53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


 
2607:f740:e626::53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


  nf3.no-ip.com / F0201-CDG-VR
204.16.253.53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


 
2620:0:2e61::53
Chicago/Illinois/United States (US) - Vitalwerks Internet Solutions, LLC


  nf4.no-ip.com / F0301-FRA-EQ
194.62.183.53
New York/United States (US) - Vitalwerks Internet Solutions, LLC


 
2a07:dc00:1830::53
Secaucus/New Jersey/United States (US) - Vitalwerks Internet Solutions, LLC


  nf5.no-ip.com / F0201-CDG-VR
204.16.253.53
Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC


 
2620:0:2e61::53
Chicago/Illinois/United States (US) - Vitalwerks Internet Solutions, LLC

net
  a.gtld-servers.net / nnn1-par6


  b.gtld-servers.net / nnn1-eltxl1


  c.gtld-servers.net / nnn1-par6


  d.gtld-servers.net / nnn1-par6


  e.gtld-servers.net / nnn1-par6


  f.gtld-servers.net / nnn1-defra-4


  g.gtld-servers.net / nnn1-defra-4


  h.gtld-servers.net / nnn1-defra-4


  i.gtld-servers.net / nnn1-defra-4


  j.gtld-servers.net / nnn1-gblon-3


  k.gtld-servers.net / nnn1-gblon-3


  l.gtld-servers.net / nnn1-gblon-3


  m.gtld-servers.net / nnn1-gblon-3


4. SOA-Entries


Domain:net
Zone-Name:net
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1707741810
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:11


Domain:net
Zone-Name:net
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1707741825
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


Domain:bounceme.net
Zone-Name:bounceme.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2016359184
Refresh:90
Retry:120
Expire:604800
TTL:60
num Entries:8


Domain:bounceme.net
Zone-Name:bounceme.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2016359186
Refresh:90
Retry:120
Expire:604800
TTL:60
num Entries:2


Domain:miao.bounceme.net
Zone-Name:bounceme.net
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2016359186
Refresh:90
Retry:120
Expire:604800
TTL:60
num Entries:2


Domain:www.miao.bounceme.net
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://miao.bounceme.net/
34.199.8.144 GZip used - 541 / 933 - 42.02 %
200

Html is minified: 127.81 %
0.216
H
Date: Mon, 12 Feb 2024 12:45:03 GMT
Server: Apache
Vary: Accept-Encoding
Connection: close
Content-Encoding: gzip
Content-Length: 541
Content-Type: text/html

• https://miao.bounceme.net/
34.199.8.144
-16

1.344
V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:34.199.8.144]:443 (34.199.8.144:443)

• http://miao.bounceme.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.199.8.144 GZip used - 593 / 1073 - 44.73 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 123.33 %
0.216

Visible Content:
Date: Mon, 12 Feb 2024 12:45:04 GMT
Server: Apache
Vary: Accept-Encoding
Connection: close
Content-Encoding: gzip
Content-Length: 593
Content-Type: text/html

• https://34.199.8.144/
34.199.8.144
-16

1.333
V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:34.199.8.144]:443 (34.199.8.144:443)

7. Comments


1. General Results, most used to calculate the result

Aname "miao.bounceme.net" is domain, public suffix is ".bounceme.net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 9144 (complete: 239099)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: miao.bounceme.net 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: miao.bounceme.net 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
AGood - only one version with Http-Status 200
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 (2 urls)
http://miao.bounceme.net/ 34.199.8.144


Url with incomplete Content-Type - header - missing charset
http://miao.bounceme.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.199.8.144


Url with incomplete Content-Type - header - missing charset
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.
Ihttp://miao.bounceme.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.199.8.144
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
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 miao.bounceme.net, 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.miao.bounceme.net

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:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 5 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 3.2 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 5 different Name Servers found: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com, 4 Name Servers included in Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, 5 Name Servers included in 1 Zone definitions: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com, 1 Name Servers listed in SOA.Primary: nf1.no-ip.com.
AGood: Only one SOA.Primary Name Server found.: nf1.no-ip.com.
AGood: SOA.Primary Name Server included in the delegation set.: nf1.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf1.no-ip.com (194.62.182.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf1.no-ip.com (2a07:dc00:1820::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf2.no-ip.com (45.54.64.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf2.no-ip.com (2607:f740:e626::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf3.no-ip.com (204.16.253.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf3.no-ip.com (2620:0:2e61::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf4.no-ip.com (194.62.183.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf4.no-ip.com (2a07:dc00:1830::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf5.no-ip.com (204.16.253.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: nf5.no-ip.com (2620:0:2e61::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.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: 5 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 5 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.: 5 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: no-ip.com
Warning: All Name Servers from the same Country / IP location.: 5 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 5 Name Servers, 3 different subnets (first Byte): 194., 204., 45., 3 different subnets (first two Bytes): 194.62., 204.16., 45.54., 4 different subnets (first three Bytes): 194.62.182., 194.62.183., 204.16.253., 45.54.64.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 5 Name Servers with IPv6, 3 different subnets (first block): 2607:, 2620:, 2a07:, 3 different subnets (first two blocks): 2607:f740:, 2620:0000:, 2a07:dc00:, 4 different subnets (first three blocks): 2607:f740:e626:, 2620:0000:2e61:, 2a07:dc00:1820:, 2a07:dc00:1830:, 4 different subnets (first four blocks): 2607:f740:e626:0000:, 2620:0000:2e61:0000:, 2a07:dc00:1820:0000:, 2a07:dc00:1830:0000:
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: nf1.no-ip.com: 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.

4. Content- and Performance-critical Checks

http://miao.bounceme.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.199.8.144
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
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: 108436 milliseconds, 108.436 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

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
http://miao.bounceme.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.199.8.144
a

1

0


0
0
0


frame

2

2


0
0
0


link
other
2

2


0
0
0


meta
other
2

0


0
0
0

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
http://miao.bounceme.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.199.8.144
a

http://178.127.20.36:80/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de


1
ok








frame
src
http://178.127.20.36:80/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de


1
http-link, change to https








frame
src
http://miao.bounceme.net/KHgKKjl_popupgoogle.html


1
http-link, change to https








link
icon
http://178.127.20.36:80/favicon.ico


1
http-link, change to https








link
shortcut icon
http://178.127.20.36:80/favicon.ico


1
http-link, change to https








meta
description



1
ok








meta
keywords



1
ok








12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com

QNr.DomainTypeNS used
1
com
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
2
nf1.no-ip.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com

Answer: ns1.no-ip.com
194.62.181.53, 2a07:dc00:1810::53

Answer: ns2.no-ip.com
194.62.180.53, 2a07:dc00:180::53

Answer: ns3.no-ip.com
204.16.255.53, 2a07:dc00:2550::53

Answer: ns4.no-ip.com
204.16.254.53, 2620:0:2e64::53
3
nf2.no-ip.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com

Answer: ns1.no-ip.com
194.62.181.53, 2a07:dc00:1810::53

Answer: ns2.no-ip.com
194.62.180.53, 2a07:dc00:180::53

Answer: ns3.no-ip.com
204.16.255.53, 2a07:dc00:2550::53

Answer: ns4.no-ip.com
204.16.254.53, 2620:0:2e64::53
4
nf3.no-ip.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com

Answer: ns1.no-ip.com
194.62.181.53, 2a07:dc00:1810::53

Answer: ns2.no-ip.com
194.62.180.53, 2a07:dc00:180::53

Answer: ns3.no-ip.com
204.16.255.53, 2a07:dc00:2550::53

Answer: ns4.no-ip.com
204.16.254.53, 2620:0:2e64::53
5
nf4.no-ip.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com

Answer: ns1.no-ip.com
194.62.181.53, 2a07:dc00:1810::53

Answer: ns2.no-ip.com
194.62.180.53, 2a07:dc00:180::53

Answer: ns3.no-ip.com
204.16.255.53, 2a07:dc00:2550::53

Answer: ns4.no-ip.com
204.16.254.53, 2620:0:2e64::53
6
nf5.no-ip.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com

Answer: ns1.no-ip.com
194.62.181.53, 2a07:dc00:1810::53

Answer: ns2.no-ip.com
194.62.180.53, 2a07:dc00:180::53

Answer: ns3.no-ip.com
204.16.255.53, 2a07:dc00:2550::53

Answer: ns4.no-ip.com
204.16.254.53, 2620:0:2e64::53
7
nf1.no-ip.com: 194.62.182.53
A
ns1.no-ip.com (2a07:dc00:1810::53)
8
nf1.no-ip.com: 2a07:dc00:1820::53
AAAA
ns1.no-ip.com (2a07:dc00:1810::53)
9
nf2.no-ip.com: 45.54.64.53
A
ns1.no-ip.com (2a07:dc00:1810::53)
10
nf2.no-ip.com: 2607:f740:e626::53
AAAA
ns1.no-ip.com (2a07:dc00:1810::53)
11
nf3.no-ip.com: 204.16.253.53
A
ns1.no-ip.com (2a07:dc00:1810::53)
12
nf3.no-ip.com: 2620:0:2e61::53
AAAA
ns1.no-ip.com (2a07:dc00:1810::53)
13
nf4.no-ip.com: 194.62.183.53
A
ns1.no-ip.com (2a07:dc00:1810::53)
14
nf4.no-ip.com: 2a07:dc00:1830::53
AAAA
ns1.no-ip.com (2a07:dc00:1810::53)
15
nf5.no-ip.com: 204.16.253.53
A
ns1.no-ip.com (2a07:dc00:1810::53)
16
nf5.no-ip.com: 2620:0:2e61::53
AAAA
ns1.no-ip.com (2a07:dc00:1810::53)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
miao.bounceme.net
0

no CAA entry found
1
0
bounceme.net
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
miao.bounceme.net

ok
1
0
_acme-challenge.miao.bounceme.net

Name Error - The domain name does not exist
1
0
_acme-challenge.miao.bounceme.net.miao.bounceme.net

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks

DomainIPPortDescriptionResultAnswer
miao.bounceme.net
34.199.8.144
21
FTP



miao.bounceme.net
34.199.8.144
21
FTP



miao.bounceme.net
34.199.8.144
22
SSH
open
SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.13

miao.bounceme.net
34.199.8.144
22
SSH
open
SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.13
Bad: SSH without DNS SSHFP Record found
Possible DNS SSHFP Entries:
miao.bounceme.net IN SSHFP 1 2 aa2ea6174868b334240826928ec32db5236c9f6b1115f46dc3cfa40549eeb401
miao.bounceme.net IN SSHFP 3 2 9063c4660050555678ab1bfceac0698840ee5249f6664373a8c1f066d5e64fb1
miao.bounceme.net IN SSHFP 4 2 108ddbbd67a0d0dda35f48d0cb39c5e3c1ad081ed13ee5dd949cde82b0d06c66
miao.bounceme.net
34.199.8.144
25
SMTP



miao.bounceme.net
34.199.8.144
25
SMTP



miao.bounceme.net
34.199.8.144
53
DNS



miao.bounceme.net
34.199.8.144
53
DNS



miao.bounceme.net
34.199.8.144
110
POP3



miao.bounceme.net
34.199.8.144
110
POP3



miao.bounceme.net
34.199.8.144
143
IMAP



miao.bounceme.net
34.199.8.144
143
IMAP



miao.bounceme.net
34.199.8.144
465
SMTP (encrypted)



miao.bounceme.net
34.199.8.144
465
SMTP (encrypted)



miao.bounceme.net
34.199.8.144
587
SMTP (encrypted, submission)



miao.bounceme.net
34.199.8.144
587
SMTP (encrypted, submission)



miao.bounceme.net
34.199.8.144
993
IMAP (encrypted)



miao.bounceme.net
34.199.8.144
993
IMAP (encrypted)



miao.bounceme.net
34.199.8.144
995
POP3 (encrypted)



miao.bounceme.net
34.199.8.144
995
POP3 (encrypted)



miao.bounceme.net
34.199.8.144
1433
MS SQL



miao.bounceme.net
34.199.8.144
1433
MS SQL



miao.bounceme.net
34.199.8.144
2082
cPanel (http)



miao.bounceme.net
34.199.8.144
2082
cPanel (http)



miao.bounceme.net
34.199.8.144
2083
cPanel (https)



miao.bounceme.net
34.199.8.144
2083
cPanel (https)



miao.bounceme.net
34.199.8.144
2086
WHM (http)



miao.bounceme.net
34.199.8.144
2086
WHM (http)



miao.bounceme.net
34.199.8.144
2087
WHM (https)



miao.bounceme.net
34.199.8.144
2087
WHM (https)



miao.bounceme.net
34.199.8.144
2089
cPanel Licensing



miao.bounceme.net
34.199.8.144
2089
cPanel Licensing



miao.bounceme.net
34.199.8.144
2095
cPanel Webmail (http)



miao.bounceme.net
34.199.8.144
2095
cPanel Webmail (http)



miao.bounceme.net
34.199.8.144
2096
cPanel Webmail (https)



miao.bounceme.net
34.199.8.144
2096
cPanel Webmail (https)



miao.bounceme.net
34.199.8.144
2222
DirectAdmin (http)



miao.bounceme.net
34.199.8.144
2222
DirectAdmin (http)



miao.bounceme.net
34.199.8.144
2222
DirectAdmin (https)



miao.bounceme.net
34.199.8.144
2222
DirectAdmin (https)



miao.bounceme.net
34.199.8.144
3306
mySql



miao.bounceme.net
34.199.8.144
3306
mySql



miao.bounceme.net
34.199.8.144
5224
Plesk Licensing



miao.bounceme.net
34.199.8.144
5224
Plesk Licensing



miao.bounceme.net
34.199.8.144
5432
PostgreSQL



miao.bounceme.net
34.199.8.144
5432
PostgreSQL



miao.bounceme.net
34.199.8.144
8080
Ookla Speedtest (http)



miao.bounceme.net
34.199.8.144
8080
Ookla Speedtest (http)



miao.bounceme.net
34.199.8.144
8080
Ookla Speedtest (https)



miao.bounceme.net
34.199.8.144
8080
Ookla Speedtest (https)



miao.bounceme.net
34.199.8.144
8083
VestaCP http



miao.bounceme.net
34.199.8.144
8083
VestaCP http



miao.bounceme.net
34.199.8.144
8083
VestaCP https



miao.bounceme.net
34.199.8.144
8083
VestaCP https



miao.bounceme.net
34.199.8.144
8443
Plesk Administration (https)



miao.bounceme.net
34.199.8.144
8443
Plesk Administration (https)



miao.bounceme.net
34.199.8.144
8447
Plesk Installer + Updates



miao.bounceme.net
34.199.8.144
8447
Plesk Installer + Updates



miao.bounceme.net
34.199.8.144
8880
Plesk Administration (http)



miao.bounceme.net
34.199.8.144
8880
Plesk Administration (http)



miao.bounceme.net
34.199.8.144
10000
Webmin (http)



miao.bounceme.net
34.199.8.144
10000
Webmin (http)



miao.bounceme.net
34.199.8.144
10000
Webmin (https)



miao.bounceme.net
34.199.8.144
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=1a3d11a0-9398-422c-8f34-9fdf06f97bbb


Last Result: https://check-your-website.server-daten.de/?q=miao.bounceme.net - 2024-02-12 13:43:51


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

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

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