Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 15. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
navanagara.com favicon

navanagara.com

In short

PhishDestroy records that navanagara.com returned a Service Unavailable error page instead of the expected site content.

“NUCB”

Review the evidence
Registrar
IndiaPDR
Resolved IP
United States162.251.85.153Unified Layer
Registered
Oct 19, 2015
First observed
Nov 1, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 15/92
VirusTotal
15 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 79
Page captures
7
open gallery
Domain age
4,030 days
registered 2015-10-19 according to WHOIS · source data differ
OTX: 1 ref Nov 1, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records that navanagara.com returned a Service Unavailable error page instead of the expected site content.

Critical
Status
Last known active
VirusTotal
15 / 92
Hosting
United States162.251.85.153Unified Layer
Registrar
IndiaPDR
Registered
Oct 19, 2015
OTX
1 community ref
Page captures
7
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page for navanagara.com shows a plain "Service Unavailable" error rather than any site content. The text explains that the server is temporarily unable to service the request due to maintenance downtime or capacity problems, and notes that a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request. No interactive elements or forms are present on this error screen.

The stored VirusTotal domain result reports 15 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".

Source evidenceVirusTotal 15 / 92 · OTX 1 references 7 sources

VirusTotal

15 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
12
Suspicious
3
Undetected
31

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
malware
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Popularity ranks

Alexa
370982

Created

First seen

DNS records

  • TTL, seconds
    14400
    Type
    A
    Value
    162.251.85.153
  • TTL, seconds
    21600
    Type
    SOA
    Responsible mailbox
    cpanel.webhostbox.net
    Value
    ns1.cp-43.webhostbox.net
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.cp-43.webhostbox.net
  • TTL, seconds
    14400
    Type
    MX
    Value
    navanagara.com
    Priority
    0
  • TTL, seconds
    14400
    Type
    TXT
    Value
    v=spf1 +a +mx +ip4:209.99.16.245 +ip4:162.251.85.153 +include:webhostbox.net ~all
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.cp-43.webhostbox.net

DNS records observed

JARM fingerprint

29d29d15d29d29d00042d42d000000cd600c085f371f8533aaf66051f8e5b1

Certificate

Subject alternative names
  • *.navanagara.com
  • navanagara.com
Issuer
Let's Encrypt / YR1
Serial
6fbd04af66a399dbd7264a230c56219c1f8
SHA-256
89eaf01a33125a2b37db9f7035d78db1315b8349a4297c2c67af0834529bf797
Subject
*.navanagara.com
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registrar IANA ID
303
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 12,
    "suspicious": 3,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "malware",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Popularity
{
    "Alexa": 370982
}
Created
2015-10-19T00:00:00Z
First seen
2023-11-02T19:53:15Z
DNS records
[
    {
        "ttl": 14400,
        "type": "A",
        "value": "162.251.85.153"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "cpanel.webhostbox.net",
        "value": "ns1.cp-43.webhostbox.net"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.cp-43.webhostbox.net"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "navanagara.com",
        "priority": 0
    },
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "v=spf1 +a +mx +ip4:209.99.16.245 +ip4:162.251.85.153 +include:webhostbox.net ~all"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.cp-43.webhostbox.net"
    }
]
Dns at
2026-10-29T14:54:10Z
Jarm
29d29d15d29d29d00042d42d000000cd600c085f371f8533aaf66051f8e5b1
Certificate
{
    "san": [
        "*.navanagara.com",
        "navanagara.com"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "6fbd04af66a399dbd7264a230c56219c1f8",
    "sha256": "89eaf01a33125a2b37db9f7035d78db1315b8349a4297c2c67af0834529bf797",
    "subject": "*.navanagara.com",
    "valid_to": "2027-01-27T12:58:02Z",
    "valid_from": "2026-10-29T12:58:03Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-10-20T09:08:14Z",
        "registration": "2015-10-19T15:49:50Z",
        "registrar expiration": "2027-10-19T15:49:50Z",
        "last update of RDAP database": "2026-10-24T07:29:28Z"
    },
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "registrar_iana_id": "303"
}
Separate source record · 12 malicious + 3 suspicious / 92 · 2026-10-29 14:53:47 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-29T14:53:47Z
fetched_at
2026-11-01T00:43:14Z
stats
{"timeout":0,"harmless":46,"malicious":12,"suspicious":3,"undetected":31}

URLScan

Malicious · engine verdict · score 79

SHA-256 bdf7b8534cab27a164a2c14b1498f7ff22e718ea754c78d21f5a494bdd49e248

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a1949d-96e5-71ac-ac3b-48b6b09b7f46

Final URL

https://navanagara.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://navanagara.com/
    From
    http://navanagara.com/
    Status
    307

IP address

162.251.85.153

Reverse DNS (PTR)

162-251-85-153.unifiedlayer.com

Contacted domains

  • maps.googleapis.com
  • fonts.googleapis.com
  • cdn.jsdelivr.net
  • cdnjs.cloudflare.com

Contacted IP addresses

  • 172.217.118.4
  • 2a00:1450:4001:c15::5f
  • 2001:4860:4845:400::
  • 104.17.24.14
  • 2606:4700::6810:b370
  • 162.251.85.153

Autonomous systems (ASN)

  • 15169
  • 13335
  • 46606

Server countries

  • US
  • DE

Linked domains

  • www.dicgc.org.in

Document hash

bdf7b8534cab27a164a2c14b1498f7ff22e718ea754c78d21f5a494bdd49e248

Script hashes

  • c90c190b73facc126891f2f132ec481e9d65f0eb550e34610e244adfaec23492
  • 6527e14ac1690f2e8b1fe033fe68d7673b27015a2affab7fe064aa39bb0f7d85
  • efcad26419c1257989e551ae58bf2692e9ef872f7883df51c39ddbb2c8c74949
  • a53c43f834b32309b084ea9314df8307e9c78cee2202c6e07f216ae4ae5b704d
  • 4bf2933ebb5813f3af1627e4bce336b0bcf0f2b09dc659493cafb823ddd51c56
  • fd8027b53a97cbd5782e85c5908e563c39776703ff9279f50658e630927b4167
  • fa87904726726364ad19a7c4b2f2b20ee10637325601b5aa88ed8bfdcb7117a7

JavaScript globals

  • $
  • jQuery
  • Popper
  • bootstrap
  • mCustomScrollbar
  • Counter
  • Swiper
  • initMap
  • google
  • module$exports$google3$maps$api$javascript$geometry$lat_lng_bounds
  • module$exports$google3$maps$api$javascript$marker$marker
  • litHtmlVersions
  • litElementVersions
  • reactiveElementVersions
  • targetElement
  • observerOptions
  • observer
  • swiper

TLS session and certificate

Subject alternative names
  • *.navanagara.com
  • navanagara.com
Cipher
AES_256_GCM
Issuer
YR1
Subject
*.navanagara.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

2916

Differs from the registration date in WHOIS (2015-10-19), which gives 4030 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Registered domain age, days

2916

Differs from the registration date in WHOIS (2015-10-19), which gives 4030 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Certificate age, days

2

Certificate validity, days

89

Page requests

38

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
79
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
nginx/1.29.8
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a1949d-96e5-71ac-ac3b-48b6b09b7f46
Final url
https://navanagara.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://navanagara.com/",
        "from": "http://navanagara.com/",
        "status": 307
    }
]
Ip
162.251.85.153
Ptr
162-251-85-153.unifiedlayer.com
Contacted domains
[
    "maps.googleapis.com",
    "fonts.googleapis.com",
    "cdn.jsdelivr.net",
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "172.217.118.4",
    "2a00:1450:4001:c15::5f",
    "2001:4860:4845:400::",
    "104.17.24.14",
    "2606:4700::6810:b370",
    "162.251.85.153"
]
Asns
[
    "15169",
    "13335",
    "46606"
]
Countries
[
    "US",
    "DE"
]
Linked domains
[
    "www.dicgc.org.in"
]
Document hash
bdf7b8534cab27a164a2c14b1498f7ff22e718ea754c78d21f5a494bdd49e248
Script hashes
[
    "c90c190b73facc126891f2f132ec481e9d65f0eb550e34610e244adfaec23492",
    "6527e14ac1690f2e8b1fe033fe68d7673b27015a2affab7fe064aa39bb0f7d85",
    "efcad26419c1257989e551ae58bf2692e9ef872f7883df51c39ddbb2c8c74949",
    "a53c43f834b32309b084ea9314df8307e9c78cee2202c6e07f216ae4ae5b704d",
    "4bf2933ebb5813f3af1627e4bce336b0bcf0f2b09dc659493cafb823ddd51c56",
    "fd8027b53a97cbd5782e85c5908e563c39776703ff9279f50658e630927b4167",
    "fa87904726726364ad19a7c4b2f2b20ee10637325601b5aa88ed8bfdcb7117a7"
]
Globals
[
    "$",
    "jQuery",
    "Popper",
    "bootstrap",
    "mCustomScrollbar",
    "Counter",
    "Swiper",
    "initMap",
    "google",
    "module$exports$google3$maps$api$javascript$geometry$lat_lng_bounds",
    "module$exports$google3$maps$api$javascript$marker$marker",
    "litHtmlVersions",
    "litElementVersions",
    "reactiveElementVersions",
    "targetElement",
    "observerOptions",
    "observer",
    "swiper"
]
Tls
{
    "san": [
        "*.navanagara.com",
        "navanagara.com"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "*.navanagara.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-27T12:58:02Z",
    "valid_from": "2026-10-29T12:58:03Z"
}
Domain age days
2916

Differs from the registration date in WHOIS (2015-10-19), which gives 4030 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Apex age days
2916

Differs from the registration date in WHOIS (2015-10-19), which gives 4030 days on the scan date 2026-11-01. The two sources disagree; both values are kept as recorded.

Tls age days
2
Tls valid days
89
Requests
38
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 79,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.29.8",
    "content-type": "text/html; charset=UTF-8"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a1277c-41e4-73c9-afff-39af267f27de
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

1 community reference

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 2 brand references · 0 classifications

Open report
Separate monitor score · 10 / 100 · 2026-11-01T01:00:46Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-11-01T01:00:46Z
source_timestamp
2026-11-01 02:00:46
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
navanagara.com — Service Unavailable error page
ai_description
PhishDestroy records that navanagara.com returned a Service Unavailable error page instead of the expected site content.
ai_summary
The captured page for navanagara.com shows a plain "Service Unavailable" error rather than any site content. The text explains that the server is temporarily unable to service the request due to maintenance downtime or capacity problems, and notes that a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request. No interactive elements or forms are present on this error screen. The stored VirusTotal domain result reports 15 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 01:48:18
revision
f04ba63362ba8ad2a36bf9a24e9b306443a467127a42434fbf15c9afbe23f7c9
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

MX records
  • navanagara.com
SPF record
v=spf1 +a +mx +ip4:209.99.16.245 +ip4:162.251.85.153 +include:webhostbox.net ~all
DKIM
  • default
DMARC
Yes
DKIM key size, bits
2048
SPF lookups
17

CAA records

Domain
navanagara.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
10
Archived days
62
Snapshots per day
0.02
Average page size, bytes
5474

Page title and metadata

Page title
NUCB
Author
SAPIENCE SIS INDIA PVT LTD.,
Keywords
Co-operative Bank
Description
Urban Co-operative Bank

Trackers

Requests
35
Observed services
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    3
  • Name
    jsDelivr
    Company
    jsDelivr
    Category
    Hosting
    Requests
    2
  • Name
    Google Maps
    Company
    Google
    Country
    US
    Category
    Utilities
    Requests
    2

Forms and mixed content

Scripts without SRI
  • https://cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.js
  • https://maps.googleapis.com/maps/api/js
Third-party scripts
2

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
467
TLS
160
Waiting
182
Connection
157
Download
155
Response time, ms
1121

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 21
  • 22
  • 25
  • 53
  • 80
  • 110
  • 143
  • 443
  • 587
  • 993
  • 995
  • 3306

Carbon estimate

Bytes
23697
CO₂, grams
0.0009
Cleaner than, %
53

DNS servers

Nameservers
  • IP address
    208.91.198.203
    Host
    ns2.cp-43.webhostbox.net
  • IP address
    208.91.198.203
    Host
    ns1.cp-43.webhostbox.net
DNS zone
navanagara.com

Location

IP address
162.251.85.153
ASN
46606
Organization
Unified Layer
City
Phoenix
Country
US

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
*.navanagara.com

DNS records

A
  • 162.251.85.153
MX
  • Mail server
    navanagara.com
    Priority
    0
NS
  • ns2.cp-43.webhostbox.net
  • ns1.cp-43.webhostbox.net
SOA
Primary nameserver
ns1.cp-43.webhostbox.net
Hostmaster
cpanel.webhostbox.net
Serial
2026102901
Refresh, seconds
3600
Retry, seconds
7200
Expiry, seconds
1209600
Minimum TTL, seconds
86400
TXT
  • v=spf1 +a +mx +ip4:209.99.16.245 +ip4:162.251.85.153 +include:webhostbox.net ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
162.251.85.153
IP version
4

Redirects

Redirect chain
  • https://navanagara.com

Page links

External link addresses
  • https://www.dicgc.org.in/
External links
1
Internal links
26

Registration record

Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.cp-43.webhostbox.net
  • ns2.cp-43.webhostbox.net

HTTP headers

Response headers
Server
nginx/1.29.8
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Mail configuration
{
    "mx": [
        "navanagara.com"
    ],
    "spf": "v=spf1 +a +mx +ip4:209.99.16.245 +ip4:162.251.85.153 +include:webhostbox.net ~all",
    "dkim": [
        "default"
    ],
    "dmarc": true,
    "dkim_bits": 2048,
    "spf_lookups": 17
}
Caa records
{
    "domain": "navanagara.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-23T19:05:16Z",
    "first": "2017-04-30T01:55:08Z",
    "changes": 10,
    "days_archived": 62,
    "scans_per_day": 0.02,
    "avg_page_bytes": 5474
}
Page title and metadata
{
    "title": "NUCB",
    "author": "SAPIENCE SIS INDIA PVT LTD.,",
    "keywords": "Co-operative Bank",
    "description": "Urban Co-operative Bank"
}
Trackers
{
    "requests": 35,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 3
        },
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 2
        },
        {
            "name": "Google Maps",
            "company": "Google",
            "country": "US",
            "category": "Utilities",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://cdn.jsdelivr.net/npm/swiper@12/swiper-bundle.min.js",
        "https://maps.googleapis.com/maps/api/js"
    ],
    "third_party_scripts": 2
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 467,
        "tls": 160,
        "wait": 182,
        "connect": 157,
        "download": 155
    },
    "response_ms": 1121
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        22,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995,
        3306
    ]
}
Carbon
{
    "bytes": 23697,
    "co2_grams": 0.0009,
    "cleaner_than": 53
}
Dns server
{
    "ns": [
        {
            "ip": "208.91.198.203",
            "host": "ns2.cp-43.webhostbox.net"
        },
        {
            "ip": "208.91.198.203",
            "host": "ns1.cp-43.webhostbox.net"
        }
    ],
    "zone": "navanagara.com"
}
Location
{
    "ip": "162.251.85.153",
    "asn": "46606",
    "org": "Unified Layer",
    "city": "Phoenix",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR1",
    "subject": "*.navanagara.com"
}
DNS records
{
    "A": [
        "162.251.85.153"
    ],
    "MX": [
        "{\"exchange\": \"navanagara.com\", \"priority\": 0}"
    ],
    "NS": [
        "ns2.cp-43.webhostbox.net",
        "ns1.cp-43.webhostbox.net"
    ],
    "SOA": "{\"nsname\": \"ns1.cp-43.webhostbox.net\", \"hostmaster\": \"cpanel.webhostbox.net\", \"serial\": 2026102901, \"refresh\": 3600, \"retry\": 7200, \"expire\": 1209600, \"minttl\": 86400}",
    "TXT": [
        "v=spf1 +a +mx +ip4:209.99.16.245 +ip4:162.251.85.153 +include:webhostbox.net ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "162.251.85.153",
    "family": 4
}
Redirects
{
    "chain": [
        "https://navanagara.com"
    ]
}
Page links
{
    "external": [
        "https://www.dicgc.org.in/"
    ],
    "external_count": 1,
    "internal_count": 26
}
Registration record
{
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "created": "2015-10-19T15:49:50Z",
    "updated": "2026-10-20T09:08:14Z",
    "expires": "2027-10-19T15:49:50Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.cp-43.webhostbox.net",
        "ns2.cp-43.webhostbox.net"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx/1.29.8",
        "content-type": "text/html; charset=UTF-8"
    }
}

Questions about navanagara.com

Is navanagara.com legit?

PhishDestroy records that navanagara.com returned a Service Unavailable error page instead of the expected site content.

Is navanagara.com safe to connect a wallet?

This report does not record which wallet requests navanagara.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used navanagara.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 7 captures

URLScan · 2026-04-26 1 / 7 Used in the analysis Source file SHA-256: 49a5bfd02e6bf891d44d7a7da89921acd97e819226f752a21422216141d4d487 SHA-256 of the prepared copy given to the model: 7cf61d5836b3b61909b31690e3954332e806a97e9bc12e5376eeee099ff9c835
SourceURLScan · 2026-04-26
Recorded
StateStored capture
Final URLhttps://cpcalendars.navanagara.com/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)

Domain details

Domain
IP Reputation United States162.251.85.153 abuse score 0/100 0 reports checked Nov 1, 2026
Registrar PDR IN(IN)
Abuse contactabuse@publicdomainregistry.com, nucb.bank@gmail.com, abuse-contact@publicdomainregistry.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for navanagara.com →
RegistrationCreated Oct 19, 2015 — Expires Oct 19, 2027
Registrant countryIndia VirusTotal WHOIS
Registrantccab55834d5b1251bbddb8911c106f11s@gmail.com VirusTotal WHOIS
WHOIS statusclientTransferProhibited
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 10/1002 brand signals
Submitted URLhttp://navanagara.com/
Observed page title
NUCB
Automated brand references
Across Gmail
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 87 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States162.251.85.153
Network ASN
AS46606
Organization
Unified Layer
Observed location
United StatesPhoenix, US
Server header
nginx/1.29.8

Nameservers 2

  • ns1.cp-43.webhostbox.net
  • ns2.cp-43.webhostbox.net

SOA

  • nsname: ns1.cp-43.webhostbox.net
  • hostmaster: cpanel.webhostbox.net
  • serial: 2026102901
  • refresh: 3600
  • retry: 7200
  • expire: 1209600
  • minttl: 86400

Mail routing 1 MX record

  • navanagara.compriority 0

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-10-29 12:58:03
Valid until
2027-01-27 12:58:02
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint89eaf01a33125a2b37db9f7035d78db1315b8349a4297c2c67af0834529bf797
Certificate names · 2 SANs
  • *.navanagara.com
  • navanagara.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 162.251.85.153rapiddns.io
Recorded subdomains8

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • autodiscover.navanagara.comDomain record
  • cpanel.navanagara.comDomain record
  • cpcalendars.navanagara.comDomain record
  • cpcontacts.navanagara.comDomain record
  • mail.navanagara.comDomain record
  • webdisk.navanagara.comDomain record
  • webmail.navanagara.comDomain record
  • www.navanagara.comDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
Chong Lua Dao
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of navanagara.com · checked Nov 1, 2026

64
Needs Work
Performance
FCP
2.63 s
First Contentful Paint
LCP
10.78 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
22 ms
Total Blocking Time
SI
7.37 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://navanagara.com/
NUCB
Urban Co-operative Bank
Response
HTTP 200
HTML body
23.1 KB
Compressed
6.5 KB
Links
35 internal · 1 external
Detected technologies
jquerynginxbootstrap
Selected response headers
Server: nginx/1.29.8
Content-Type: text/html; charset=UTF-8
Cache-Control: no-store, no-cache, must-revalidate, max-age=0, post-check=0, pre-check=0
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: bdf7b8534cab27a164a2c14b1498f7ff22e718ea754c78d21f5a494bdd49e248
Saved response-header values · 11
Cache-Control
no-store, no-cache, must-revalidate, max-age=0, post-check=0, pre-check=0
Content-Encoding
gzip
Content-Length
8224
Content-Type
text/html; charset=UTF-8
Date
Sun, 01 Nov 2026 00:51:24 GMT
Expires
Wed, 01 Jan 2014 00:00:00 GMT
Pragma
no-cache
Server
nginx/1.29.8
Vary
Accept-Encoding
X-Proxy-Cache
MISS
X-Server-Cache
true

Values retained by the collector; long values may be shortened during collection.

Archived

Captured network requests

Network requests: 38 SHA-256 hashes: 38 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-01 01:05 UTC.

Open this scan on URLScan 01a1949d-96e5-71ac-ac3b-48b6b09b7f46 ↗

All retained availability observations1

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 01:43:40.371190
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    navanagara.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Automated brand label: Gmail · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 79
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 15/92
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • Automated brand label: Gmail
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. URLScan

    Page captured

    View source
  2. Wayback Machine

    Page archived

    View source
  3. AlienVault OTX

    1 community references

    View source
  4. Added to PhishDestroy

    navanagara.com

    View source
  5. VirusTotal

    15/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

navanagara.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 15 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 1 ref WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including navanagara.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/navanagara.com"
  title="PhishDestroy threat report for navanagara.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>