Skip to content

Hostname

linkedbd.com

Last fetched

linkedbd.com resolves to 172.241.213.97, announced in 172.241.212.0/22 by LEASEWEB-USA-LAX - Leaseweb USA, Inc. in US. linkedbd.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · linkedbd.comRouting diversity3.9/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint7.4/10canon.whisper.security/host/linkedbd.com

Resolution chain

IPv6 resolution

No AAAA record for linkedbd.com is recorded in WhisperGraph.

Attribution

leaseweb usa

ORIGIN_AS

WHOIS identity

Registrar
iana:1479
Registrant organisation
domain administrator
Contact emails
linkedbd.com@yourjungleprivacy.com, info@improsys.com, linkedbd@yahoo.com, pw-1b9a70d6c184fbfef11390c877d39b9a@privacyguardian.org, pw-49f3aa49fd01ef52e9e2cf5877f0a56c@privacyguardian.org, pw-531b431fc3283dd3375c60264171921d@privacyguardian.org, pw-6569e480d0bd8a3ccc197fe9e8cc2ad4@privacyguardian.org, pw-7af4bb86e5ba490e7c158adb202fe42b@privacyguardian.org, pw-adcce0b2781c30ce6d7c7e604b939d2f@privacyguardian.org, pw-ae64c5a2640c319f240b8b3a5255869e@privacyguardian.org

Subdomains

Showing 3 of 3 subdomains (3 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns1.brainydns.com
  • ns2.brainydns.com
  • ns1.emu-dns.com
  • ns1.kirklanddc.com
  • ns2.kirklanddc.com
  • ns1.koaladns.com
  • ns2.koaladns.com
  • ns1.magpiedns.com
  • ns2.magpiedns.com
  • ns1.numbatdns.com
  • ns1.squirreldns.com
  • ns2.squirreldns.com

MX records

  • mx156.hostedmxserver.com

Threat-feed evidence

History

Related pages

Pivot from linkedbd.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: "linkedbd.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.