Hostname
beccltd.com
Last fetched
beccltd.com resolves to 103.48.119.159, announced in 103.48.119.0/24 by XEON-BD - XeonBD in BD. beccltd.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for beccltd.com is recorded in WhisperGraph.
Attribution
xeonbd
ORIGIN_AS
WHOIS identity
- Registrar
- iana:93
- Registrant organisation
- link3 technologies
- Contact emails
- 137e561ed5f957b1cbafb01db5967c0fbbd965de@whois.gkg.net, 40d0d466ace9725bd4b8982198b4e30fb774b9fd@whois.gkg.net, 4111a1e5dff88c386b9fbb355010b4b315f395ec@whois.gkg.net, 4299ab2c217f3eb2f0f37b4679c5623923b493b2@whois.gkg.net, 55a068b2d4a3488fdcb480c8c15eafc556dd2e99@whois.gkg.net, 56ca6e3a839b4abf7d5cee7b10a88231cfb56ca9@whois.gkg.net, 5bda8e35d46a19baa2d39fa013049eef1df294da@whois.gkg.net, 5be8ecbf9f9e93fff48e8e8fc63aa8fd2e7d99f3@whois.gkg.net, 64a0339a5e11798688bc3f3ba2ea8f6addf10d2c@whois.gkg.net, 6f9ff321a3a777c1dbb1d4ff2b9287e64527ffbb@whois.gkg.net, 71dca55882fcbbd506f382c65d7a95bfc3cfb627@whois.gkg.net, 936abcd4161b395375ef603ab042701880cf37af@whois.gkg.net, 9b3c4c8ae75131e8ed6f82c6c192d8014547f6a1@whois.gkg.net, a2015b6f2982eebbd384377a6314dd36b2b1aaf5@whois.gkg.net, a2eaaea5e5fdfea8d781d8911c4801a72921d7fe@whois.gkg.net, b84bca1f00609ea0dddd422f7867e22dbcfa7214@whois.gkg.net, cab7130192972eec62e6e9db8aa5a71fa3ee745c@whois.gkg.net, d6281a298f4c0f6e57e93871ecb5a5ecd9b40674@whois.gkg.net, e28f24ac0ba13322978ce1a5382428a292b3babb@whois.gkg.net, shamim@link3.net
Subdomains
Mail and authentication
Nameservers
- ns1.xeonbd.com
- ns2.xeonbd.com
MX records
- mxcloud1.xeonbd.com
- mxcloud2.xeonbd.com
- mxcloud3.xeonbd.com
- mxcloud4.xeonbd.com
SPF policy
- include: spf.antispamcloud.com
- a: beccltd.com
- mx: beccltd.com
- a: spf.xeonbd.com
- ip: 103.48.119.100
Threat-feed evidence
History
Related pages
Pivot from beccltd.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: "beccltd.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.