Skip to content

Hostname

bd-times.com

Last fetched

bd-times.com resolves to 15.197.240.20, announced in 15.197.240.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. bd-times.com is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:55:39 GMT
Last seen on a feed
Sun, 13 Sep 2026 20:06:23 GMT

Nutrition Label

WHISPER CANON · bd-times.comRouting diversity2.4/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/bd-times.com

Resolution chain

IPv6 resolution

No AAAA record for bd-times.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
codex software solution
Contact emails
codexsoftwaresolution@gmail.com, b944f264b6d643beaa869f1e62da2471.protect@whoisguard.com, contact@privacyprotect.org, 150dd4a76b64bebfd3cfed4cc011c259ee7efeea72c0db891fd979558cfc722f@bd-times.com.whoisproxy.org, 21667bf41554659723eca4293e2ec898b976491862389c0743b0ddf5037ab49c@bd-times.com.whoisproxy.org, 310a291121a7bed21c4d9102423c9d624ce01b622b839151f98a74776037cfc2@bd-times.com.whoisproxy.org, 73de3ccdc5ac2fdf1a885e43e7a3599dbb564fd990396947003463394bce1397@bd-times.com.whoisproxy.org, e5a1550693e90987ce6a756595e19ef902986f2a6ed1dc433c4becc24b41a9a0@bd-times.com.whoisproxy.org, fba187d6d735bac56035665487404142b44e5356048348b8abd372f86a5ea090@bd-times.com.whoisproxy.org

Subdomains

Mail and authentication

Nameservers

  • dns11.banglabee.com
  • dns12.banglabee.com
  • dns3.parkpage.foundationapi.com
  • dns4.parkpage.foundationapi.com
  • ns1.verification-hold.suspended-domain.com

MX records

  • bd-times.com

Threat-feed evidence

History

Related pages

Pivot from bd-times.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "bd-times.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.