SSL Check WHOIS
Dashboard / Security Report

pushd.com

Add this badge to your site

Shows this report's grade and links back to it. It is read from the stored report, never a new scan; a report older than 30 days also shows the month it was checked.

pushd.com: SSL/TLS grade B (HTTPS Monitor)pushd.comB
IPv6: no public AAAA record — the domain is reachable over IPv4 only.
All 5 endpoints share identical configuration Select an IP for owner, ASN & location
B 18.213.160.53 IPv4 WHOIS › B 34.231.9.12 IPv4 WHOIS › B 34.237.117.30 IPv4 WHOIS › B 34.237.134.29 IPv4 WHOIS › B 54.205.19.49 IPv4 WHOIS ›

Grade Breakdown

Protocol Support 50%
Key Exchange 90%
Cipher Strength 100%
Certificate 100%
Grade capped at B: server supports obsolete TLS 1.0/1.1.

Security Vulnerabilities Detected

  • •Obsolete TLS versions (1.0/1.1) supported.
  • •CBC cipher suites with TLS 1.0/1.1 (BEAST, Lucky13).

Protocol Configuration

Supported Protocols

TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3
SSL 2

Negotiated Cipher

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

Protocol Details

Connection
ALPN h2 http/1.1
SNI Required Yes
Supported Named Groups secp256r1 (inferred)
Post-Quantum Key Exchange No (no hybrid ML-KEM group such as X25519MLKEM768)
HTTP/3 (QUIC) No
Encrypted Client Hello No
Security Features
Forward SecrecyYes (ECDHE / DHE)
Downgrade Prevention Unknown
Secure Renegotiation Supported (RFC 5746)
Extended Master Secret Yes (RFC 7627)
OCSP Stapling No
HSTS Yes 2 years · includeSubDomains
HSTS Preloading Not preloadedSubmit →
Security Checks
BEAST attack Not mitigated server-side (TLS 1.0 + CBC)
POODLE (SSLv3) No (SSL 3 not supported)
POODLE (TLS) Possible (CBC + legacy TLS present)
RC4 No
SSL/TLS CompressionNo (not supported by .NET TLS stack)
HeartbleedNot tested

Cipher Suite Analysis

Cipher SuiteHexKey ExchangeFSBitsStrength
# TLS 1.2
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA2560xC02FECDHEFS128Secure
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA2560xC027ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA0xC013ECDHEFS128Weak
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3840xC030ECDHEFS256Secure
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA3840xC028ECDHEFS256Weak
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA0xC014ECDHEFS256Weak
TLS_RSA_WITH_AES_128_GCM_SHA2560x009CRSANo FS128Weak
TLS_RSA_WITH_AES_128_CBC_SHA2560x003CRSANo FS128Weak
TLS_RSA_WITH_AES_128_CBC_SHA0x002FRSANo FS128Weak
TLS_RSA_WITH_AES_256_GCM_SHA3840x009DRSANo FS256Weak
TLS_RSA_WITH_AES_256_CBC_SHA2560x003DRSANo FS256Weak
TLS_RSA_WITH_AES_256_CBC_SHA0x0035RSANo FS256Weak

Handshake Simulation

ClientProtocolCipher SuiteResult
Chrome 120 / Win 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Chrome 80 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Firefox 115 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
iOS 17 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
macOS 14 / SafariTLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 14TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Chrome 69 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Chrome 49 / XP SP3TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 10TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
IE 11 / Win 7TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 9.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 7.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 5.0TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.4.2TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 11TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Java 8u121TLS 1.2TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256Success
Android 4.0.4TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess
Android 4.1.1TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess
Baidu Jan 2015TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess
Java 6TLS 1.0TLS_ECDHE_RSA_WITH_AES_128_CBC_SHASuccess

* Simulated based on server's supported protocols and cipher configuration.

Site Access: HTTP and HTTPS

What a visitor typing each address gets, and where its redirects end (up to 5 are followed), as seen from our scanner.

Hosthttp:// (port 80)https:// (port 443)
pushd.com301 → https://auraframes.com/ → … → https://auraframes.be/ → 200 OK301 → https://auraframes.com/ → … → https://auraframes.be/ → 200 OK
www.pushd.com301 → https://auraframes.com/ → … → https://auraframes.be/ → 200 OK301 → https://auraframes.com/ → … → https://auraframes.be/ → 200 OK
  • http://pushd.com redirects to HTTPS.
  • https://pushd.com forwards visitors to auraframes.com, a different site. View its report ›

DNS Records

As a public resolver answered for pushd.com. Looked up 2026-11-22 01:58 UTC · today

TypeRecords
A
AAAA None
NS
ns-1534.awsdns-63.org ns-1886.awsdns-43.co.uk ns-3.awsdns-00.com ns-747.awsdns-29.net
MX
1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com
SPF
v=spf1 include:_spf.google.com include:spf.mandrillapp.com include:mail.zendesk.com include:sendgrid.net ~all

Certificate Identity

Common Namepushd.com
Alt Names *.auraframes.com *.aura.gift auraframes.com *.giveaura.com *.pushd.com giveaura.com aura.gift auranow.com pushd.com *.auranow.com
IssuerCN=Amazon RSA 2048 M01, O=Amazon, C=US
Validity 2026-10-16 to 2027-05-01 (160 days remaining)
KeyRSA 2048 bits (sha256RSA)
Serial Number018EBD379ED67EA98CDAF24A2C257BF1
SHA256 Fingerprint 26a3b8a049fa94fa973ac1d89106855a549aac88d18d4f8b956962bbcc97142c
Pin SHA256X0PKk9i7phBSXsLzFbWwMbUlUo74Qy1Gm09NVS+/6/o=

Certificate Properties

Type DV Domain Validated
Cert Transparency Yes (SCT)
OCSP Must Staple No
Revocation Good (not revoked) OCSP: http://ocsp.r2m01.amazontrust.com CRL: http://crl.r2m01.amazontrust.com/r2m01.crl
DNS CAA No (missing)
Trusted By Yes Mozilla · Apple · Android · Java · Windows
Name Match Yes
Validity Period 198 days (maximum 200 days for certificates issued then)
Chain IssuesNone

Trust Chain Architecture

End-Entity Certificate
CN=*.auraframes.com (Issuer: CN=Amazon RSA 2048 M01, O=Amazon, C=US)
Intermediate CA
CN=Amazon RSA 2048 M01, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)
Root Certificate
CN=Amazon Root CA 1, O=Amazon, C=US (Issuer: CN=Amazon Root CA 1, O=Amazon, C=US)

TLS History & Relations

Everything our scans have seen for pushd.com, first seen 2026-10-09; current certificate since 2026-11-22.

Certificates served

Certificate (SHA-256)IssuerValidServed
26a3b8a049fa94fa… current Amazon RSA 2048 M012026-10-16 → 2027-05-012026-11-22

Addresses

AddressCertificateSeen
18.213.160.53 26a3b8a049fa94fa… 2026-11-22
34.231.9.12 26a3b8a049fa94fa… 2026-11-22
34.237.117.30 26a3b8a049fa94fa… 2026-11-22
34.237.134.29 26a3b8a049fa94fa… 2026-11-22
54.205.19.49 26a3b8a049fa94fa… 2026-11-22

TLS history (a row per change; repeated checks only extend it)

Since → last checked (UTC)GradeTLSCertificatesAddresses
2026-11-22 01:58BTLS 1.2 26a3b8a049fa94fa… 18.213.160.53, 34.231.9.12, 34.237.117.30, 34.237.134.29, 54.205.19.49

Other domains on the same certificate