DNS report
aeza.net
Complete DNS, mail, web and security analysis.
DNS cache tools
If you have recently made DNS changes and they are not yet reflected in the report, you can try to flush the DNS cache of these public resolvers: The domain name will be copied to your clipboard automatically when clicking on a button
| Category | Status | Test | Details | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
WHOIS0.2 ms |
Domain Status |
Source: WHOIS (port 43) whois.reg.com
Registrar lock enabled The domain exposes a transfer lock status, such as clientTransferProhibited or serverTransferProhibited. |
|||||||||||||||||||||||||||||||||||||
|
PARENT0.0 ms |
Domain NS records |
Nameserver records returned by the parent servers are:
ns1.edgeam.am [5.101.71.71, 2a13:1ec0:1000::1071] (NO GLUE) [TTL=172800] ns2.edgeam.am [5.101.71.72, 2a13:1ec0:1000::1072] (NO GLUE) [TTL=172800] m.gtld-servers.net was kind enough to give us that information. |
|||||||||||||||||||||||||||||||||||||
| TLD Parent Check |
m.gtld-servers.net has information for your TLD.
This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check. |
||||||||||||||||||||||||||||||||||||||
| Your nameservers are listed |
Mismatch between parent and domain NS.
|
||||||||||||||||||||||||||||||||||||||
| DNS Parent sent Glue |
0 of 2 nameservers sent GLUE.
The parent nameserver a.gtld-servers.net is not sending out GLUE for every nameserver listed, meaning it is sending your nameserver hostnames without their corresponding A records. This is acceptable, but it requires an extra A record lookup, which may slightly delay DNS resolution. This often occurs when nameservers are on a different TLD (e.g., domain.com with nameserver ns.otherdomain.com). |
||||||||||||||||||||||||||||||||||||||
| Nameservers A records |
Every nameserver listed has A records.
This is a must if you want to be found. |
||||||||||||||||||||||||||||||||||||||
|
NS6287.6 ms |
NS records from your NameServers |
NS records returned by the currently delegated nameservers are:
All NS records have the same TTL: 300 seconds. |
|||||||||||||||||||||||||||||||||||||
| Public Resolver |
|
||||||||||||||||||||||||||||||||||||||
| Mismatched NS records |
Mismatch detected between parent and zone NS records.
Parent NS: ns1.edgeam.am ns2.edgeam.am Zone NS: ns1.edgedns.ru ns2.edgedns.world |
||||||||||||||||||||||||||||||||||||||
| DNS servers responded |
All nameservers listed at the parent server responded.
|
||||||||||||||||||||||||||||||||||||||
| Name of nameservers are valid |
All of the NS records that your nameservers report seem valid.
|
||||||||||||||||||||||||||||||||||||||
| Multiple Nameservers |
You have 2 nameservers. This is acceptable, but having 3 or more is recommended according to RFC2182 section 5.
Having 2 nameservers is ok by me. |
||||||||||||||||||||||||||||||||||||||
| Missing nameservers reported by parent |
FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1).
The missing NS records at the parent are: ns1.edgedns.ru ns2.edgedns.world You need to make sure that these nameservers are working. If they are not working correctly, you may experience problems. |
||||||||||||||||||||||||||||||||||||||
| Missing nameservers reported by your nameservers |
ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers.
The problem NS records are: ns1.edgeam.am ns2.edgeam.am This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example). |
||||||||||||||||||||||||||||||||||||||
| Domain CNAMEs |
OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
|
||||||||||||||||||||||||||||||||||||||
| NSs CNAME check |
OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
|
||||||||||||||||||||||||||||||||||||||
| Different subnets |
You have nameservers on different subnets.
|
||||||||||||||||||||||||||||||||||||||
| Recursive Queries |
ns1.edgedns.ru → ✅ does not allow recursion (good)
ns2.edgedns.world → ✅ does not allow recursion (good) |
||||||||||||||||||||||||||||||||||||||
| Same Glue |
Mismatch between parent GLUE and zone A records:
ns1.edgeam.am → Parent: 5.101.71.71, 2a13:1ec0:1000::1071 | Zone: ns2.edgeam.am → Parent: 5.101.71.72, 2a13:1ec0:1000::1072 | Zone: Make sure both match to comply with DNS best practices. |
||||||||||||||||||||||||||||||||||||||
| NS Self-IP Consistency |
All nameservers return consistent IP addresses with what they declare in the zone.
|
||||||||||||||||||||||||||||||||||||||
| Glue for NS records |
GLUE was not sent when I asked your nameservers for your NS records.
This is ok but you should know that in this case an extra A record lookup is required. The nameservers without glue are: 5.188.176.176 5.101.71.71 You can fix this by adding A records to your nameservers. |
||||||||||||||||||||||||||||||||||||||
| Nameservers are lame |
All the nameservers listed at the parent servers answer authoritatively for your domain.
|
||||||||||||||||||||||||||||||||||||||
| IPs of nameservers are public |
Ok. Looks like the IP addresses of your nameservers are public.
This is a good thing because it will prevent DNS delays and other problems. |
||||||||||||||||||||||||||||||||||||||
| DNS servers allow TCP connection |
OK. Seems all your DNS servers allow TCP connections.
This is a good thing and useful even if UDP connections are used by default. |
||||||||||||||||||||||||||||||||||||||
| Different autonomous systems |
Authoritative name servers are spread across multiple autonomous systems:
ns1.edgedns.ru → AS210756 ns2.edgedns.world → AS201589 |
||||||||||||||||||||||||||||||||||||||
| Stealth NS records sent |
The following name servers are configured in your zone but not reported by the parent (stealth NS):
ns1.edgedns.ru ns2.edgedns.world Stealth name servers can cause inconsistent DNS answers and complicate troubleshooting. Make sure all authoritative NS are correctly published at the registry/parent level. |
||||||||||||||||||||||||||||||||||||||
|
DNSSEC728.0 ms |
Zone signed |
DNSSEC: Unsigned
No RRSIG record found. The zone is not signed with DNSSEC. |
|||||||||||||||||||||||||||||||||||||
| DNSKEY records |
No DNSKEY records found.
|
||||||||||||||||||||||||||||||||||||||
| DS record in parent |
No DS record found in the parent zone.
|
||||||||||||||||||||||||||||||||||||||
| NSEC/NSEC3 record |
No NSEC or NSEC3 record found when querying a non-existent subdomain.
This may indicate a misconfiguration or lack of proper DNSSEC denial-of-existence support. |
||||||||||||||||||||||||||||||||||||||
|
SOA0.1 ms |
SOA Record |
The SOA (Start of Authority) record is:
Primary nameserver: ns1.edgedns.ru Hostmaster E-mail address: support@edgecenter@ru Serial #: 1790700838 Refresh: 5400 Retry: 3600 Expire: 1209600 Default TTL: 300 |
|||||||||||||||||||||||||||||||||||||
| NSs have same SOA serial |
OK. All your nameservers agree that your SOA serial number is 1790700838.
|
||||||||||||||||||||||||||||||||||||||
| SOA MNAME entry |
ns1.edgedns.ru is NOT listed at the parent level. This could cause issues with zone transfer or delegation.
|
||||||||||||||||||||||||||||||||||||||
| SOA Serial |
Your SOA serial number is: 1790700838. This appears to follow the recommended YYYYMMDDnn format.
|
||||||||||||||||||||||||||||||||||||||
| SOA REFRESH |
Your SOA REFRESH interval is: 5400. OK.
|
||||||||||||||||||||||||||||||||||||||
| SOA RETRY |
Your SOA RETRY value is: 3600. OK.
|
||||||||||||||||||||||||||||||||||||||
| SOA EXPIRE |
Your SOA EXPIRE number is: 1209600. Looks OK.
|
||||||||||||||||||||||||||||||||||||||
| SOA MINIMUM TTL |
Minimum TTL is low (300). Recommended: 1h+ (3600).
A low minimum TTL results in more frequent DNS queries, which can increase server load. A higher value improves cache efficiency. |
||||||||||||||||||||||||||||||||||||||
|
MX ... |
MX Records |
|
|||||||||||||||||||||||||||||||||||||
|
TXT0.1 ms |
TXT Records |
|
|||||||||||||||||||||||||||||||||||||
|
SPF ... |
SPF Analysis |
|
|||||||||||||||||||||||||||||||||||||
|
DMARC71.7 ms |
DMARC Configuration |
DMARC Record was found:
v=DMARC1;p=quarantine;rua=mailto:[email protected] Policy summary:
v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:[email protected]; ruf=none; fo=0; pct=100; adkim=r; aspf=r; ri=86400; rf=afrf; DMARC Evaluation Score: 1.5/3 To improve your score:
|
|||||||||||||||||||||||||||||||||||||
|
MTA-STS / TLS-RPT435.8 ms |
Mail TLS security |
MTA-STS score 0/5 Recommendations:
|
|||||||||||||||||||||||||||||||||||||
|
DKIM ... |
DKIM Records Detected |
|
|||||||||||||||||||||||||||||||||||||
|
BIMI121.7 ms |
BIMI Record |
No BIMI record found at: default._bimi.aeza.net.
|
|||||||||||||||||||||||||||||||||||||
|
SSL ... |
SSL Certificate Summary |
|
|||||||||||||||||||||||||||||||||||||
|
CAA ... |
CAA Records |
|
|||||||||||||||||||||||||||||||||||||
|
HSTS ... |
HSTS |
|
|||||||||||||||||||||||||||||||||||||
|
HTTPS ... |
HTTPS |
|
|||||||||||||||||||||||||||||||||||||
|
HTTPS (DNS) ... |
HTTPS DNS record |
|
|||||||||||||||||||||||||||||||||||||
|
WWW ... |
A Record |
|
|||||||||||||||||||||||||||||||||||||
|
AXFR (Zone Transfer)505.7 ms |
AXFR status for the zone |
AXFR is refused by the authoritative nameservers for aeza.net.
Nameservers tested: ns1.edgedns.ru, ns2.edgedns.world |
|||||||||||||||||||||||||||||||||||||
| Security note |
Zone transfers (AXFR) should be disabled in production unless explicitly required and restricted.
Leaving AXFR open allows anyone to enumerate your entire DNS zone (subdomains, MX, TXT, internal hosts, etc.). |
||||||||||||||||||||||||||||||||||||||
|
PORTS ... |
Open ports detected (95.181.177.125) |
|
|||||||||||||||||||||||||||||||||||||
|
REPUTATION ... |
IP in blacklists (95.181.177.125) |
|
|||||||||||||||||||||||||||||||||||||
|
DNS found ... |
|
||||||||||||||||||||||||||||||||||||||
| Test | Details | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Website Preview0.0 ms
|
Snapshot is generated through DNSprobe's rendering proxy and may be served from a short cache.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Security Headers20010.8 ms
|
Score: 5/100 (F) Failing, very weak or absent security headers
Recommended starter configuration (.htaccess) Starter configuration to copy and adapt. CSP, CORS and cookie rewriting are intentionally commented because they can break some sites if enabled blindly. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
WHOIS456.5 ms
|
Source: WHOIS (port 43) whois.reg.com
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
RDAP 456.2 ms
|
Source: RDAP rdap.org → rdap.verisign.com → rdap.reg.com
Registrar
RDAP JSON (raw){
"objectClassName": "domain",
"handle": "2645461759_DOMAIN_NET-VRSN",
"ldhName": "AEZA.NET",
"links": [
{
"value": "https://rdap.verisign.com/net/v1/domain/aeza.net",
"rel": "self",
"href": "https://rdap.verisign.com/net/v1/domain/aeza.net",
"type": "application/rdap+json"
},
{
"value": "https://rdap.verisign.com/net/v1/domain/aeza.net",
"rel": "related",
"href": "https://rdap.reg.com/rdap/domain/AEZA.NET",
"type": "application/rdap+json"
}
],
"status": [
"client transfer prohibited"
],
"entities": [
{
"objectClassName": "entity",
"handle": "1606",
"roles": [
"registrar"
],
"links": [
{
"href": "http://www.reg.ru",
"type": "text/html",
"value": "https://rdap.reg.com/rdap/",
"rel": "about"
}
],
"publicIds": [
{
"type": "IANA Registrar ID",
"identifier": "1606"
}
],
"vcardArray": [
"vcard",
[
[
"version",
[],
"text",
"4.0"
],
[
"fn",
[],
"text",
"Registrar of Domain Names REG.RU LLC"
]
]
],
"entities": [
{
"objectClassName": "entity",
"roles": [
"abuse"
],
"vcardArray": [
"vcard",
[
[
"version",
[],
"text",
"4.0"
],
[
"fn",
[],
"text",
""
],
[
"tel",
{
"type": "voice"
},
"uri",
"tel:+74955801111"
],
[
"email",
[],
"text",
"[email protected]"
]
]
]
}
]
}
],
"events": [
{
"eventAction": "registration",
"eventDate": "2021-10-04T17:28:31Z"
},
{
"eventAction": "expiration",
"eventDate": "2027-10-04T17:28:31Z"
},
{
"eventAction": "last changed",
"eventDate": "2026-09-22T13:35:56Z"
},
{
"eventAction": "last update of RDAP database",
"eventDate": "2026-10-22T12:01:05Z"
}
],
"secureDNS": {
"delegationSigned": false
},
"nameservers": [
{
"objectClassName": "nameserver",
"ldhName": "NS1.EDGEAM.AM"
},
{
"objectClassName": "nameserver",
"ldhName": "NS2.EDGEAM.AM"
}
],
"rdapConformance": [
"rdap_level_0",
"icann_rdap_technical_implementation_guide_1",
"icann_rdap_response_profile_1"
],
"notices": [
{
"title": "Terms of Service",
"description": [
"Service subject to Terms of Use."
],
"links": [
{
"href": "https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml",
"type": "text/html",
"value": "https://rdap.verisign.com/net/v1/domain/aeza.net",
"rel": "terms-of-service"
}
]
},
{
"title": "Status Codes",
"description": [
"For more information on domain status codes, please visit https://icann.org/epp"
],
"links": [
{
"href": "https://icann.org/epp",
"type": "text/html",
"value": "https://rdap.verisign.com/net/v1/domain/aeza.net",
"rel": "glossary"
}
]
},
{
"title": "RDDS Inaccuracy Complaint Form",
"description": [
"URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"
],
"links": [
{
"href": "https://icann.org/wicf",
"type": "text/html",
"value": "https://rdap.verisign.com/net/v1/domain/aeza.net",
"rel": "help"
}
]
}
]
} |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
You like this tool?
Processed in 0.009 seconds.
Made with with PHP and a bit of JS.
Made with with PHP and a bit of JS.
Lines of code: 20,304
