Skip to content
https://unrealengine.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
3 PASS 4 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.unrealengine.com/
200https://unrealengine.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://unrealengine.com/ http://www.unrealengine.com:80/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
1 redirect(s), 1477 ms total
REVIEW
1 redirect(s), 1477 ms total
Info::
Single redirect
Got: https://unrealengine.com → https://www.unrealengine.com:443/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1477 ms total
Got: 1477 ms

https://unrealengine.com

897 ms · HTTP/1.1

301

https://www.unrealengine.com:443/

580 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unrealengine.com301897 msHTTP/1.1awselb/2.0
2https://www.unrealengine.com:443/200580 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
HTTP Probe Timing
Total 933 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
198 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
244 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
246 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
933 ms
Total Time Total request time from DNS lookup through full response.
933 ms

Connection waterfall

DNS Lookup 198 ms TCP Connect 244 ms TLS Handshake 246 ms Server Processing 245 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
182 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

182
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
3 A records, 100 ms lookup
PASS
3 A records, 100 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 34.202.56.41, 3.216.119.0, 32.193.137.124
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1501.awsdns-59.org, ns-1839.awsdns-37.co.uk, ns-645.awsdns-16.net, ns-95.awsdns-11.com
Info::
5 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 100 ms
Got: 100 ms
A34.202.56.41, 3.216.119.0, 32.193.137.124
AAAA
CNAME
NSns-1501.awsdns-59.org, ns-1839.awsdns-37.co.uk, ns-645.awsdns-16.net, ns-95.awsdns-11.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
_bppsoy5gjtgj229uhlg9uwo54xvo6el
_hihqzyt55go13gkrs5y93ungn4hh0b0
dropbox-domain-verification=xgob8jkatvke
facebook-domain-verification=xtughlq76ut5f2pr6y2efwwlks2zmu
google-site-verification=9JwJst2duDC1keUh9SCgsSd63tPy5cT6NrZ3VyatKew
google-site-verification=DcQ50BWoaX9lQrJkvcpoSiWXJm6hj04WGG5dlokEpCY
google-site-verification=JyGhQT0aWk6veMXg6G4Z7L8gWcHN1H1Ld8HWTxq4Egw
google-site-verification=QNsykUXP67dCuXXj8npgLwDnjNUDphqvDRM1PDCgwGQ
google-site-verification=RQGWad6moDNsTzv0QyEQmDJav6D8RC78vmWMicwApZw
google-site-verification=XRT98nvNEL5jiVkTZBzKdWyI1d82UE689jLKyMGErfY
google-site-verification=dJWG2YOwL3aZXgCnKmAqnBZOeEiJj76Nfu25qGm0dqg
google-site-verification=elhj3pOwDLlKQrGV2GRNr1P9F0F3rRxNMorHJeiB0NU
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
CAALookup not available with standard resolver
Resolved in 100 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Crawlability
robots.txt present, sitemap with 3393 URLs
PASS
robots.txt present, sitemap with 3393 URLs
Info::
robots.txt is present
Got: 415 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3393 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 415 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Disallow: /portal*
Disallow: /register*
Disallow: /account*
Disallow: /dashboard*
Disallow: /id*
Disallow: /v1/developers*
Disallow: /internal/*
Disallow: /*/try-free*
Disallow: /*/search
Disallow: /*?tags=
Disallow: /*&tags=
Disallow: /*?filter=
Disallow: /*&filter=
Disallow: /*?keyword=
Disallow: /*&keyword=
Disallow: /*?skip=
Disallow: /*&skip=

Sitemap: https://www.unrealengine.com/sitemap.xml

A+
Domain Intelligence
unrealengine.com — via MarkMonitor Inc., 28 years, 2 months old, hosted on AWS
PASS
unrealengine.com — via MarkMonitor Inc., 28 years, 2 months old, hosted on AWS
Info::
Domain registered until Nov 20, 2027 (1 years, 7 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

490 days

November 20, 2027

SSL certificate

182 days

Issued by Amazon

Domain age

28 years, 2 months

Registered July 1, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

3.216.119.0

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created July 1, 1998 (28 years, 2 months ago)
Expires November 20, 2027 (1 years, 7 months)
Last Updated October 19, 2025
Name Servers ns-1501.awsdns-59.org, ns-1839.awsdns-37.co.uk, ns-645.awsdns-16.net, ns-95.awsdns-11.com
DNSSEC Not enabled
Hosting
IP Address 3.216.119.0
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (1.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback