The race car is gearing up for a public launch on 9 September in DCU.

A team of students from Dublin City University (DCU) has designed and built Ireland’s first solar-powered racing car.

The custom-engineered car, which relies entirely on solar energy and clean battery storage, recently under underwent track validation and high-speed testing at Kildare’s Mondello Park motor racing circuit.

After receiving the green light in a test drive today (27 August), the car is now ready for a public launch on 9 September in DCU.

The “ultra-efficient” single-seater vehicle features a six-metre ‘bullet’ model frame that’s been designed for maximum power conversion and minimal drag, the university said. It is equipped with custom solar array architecture, designed with lightweight composite materials and bespoke telemetry systems.

The entire process – from designing to completing a successful test run – took the DCU Solar Racing team four years, and required intensive research, prototyping and aerodynamic testing.

More than 40 multidisciplinary students, spanning mechanical, electrical, software engineering and business operations, contributed to the project, DCU said.

The Solar Racing team is now gearing up to represent Ireland at the iLumen European Solar Challenge, a 24-hour endurance competition for solar vehicles, set to take place this September at Circuit Zolder in Belgium.

It is the largest race of its kind in Europe, and second largest globally – only behind the 3,000km-long World Solar Challenge in Australia.

The Solar Racing team is sponsored by more than 30 organisations including DCU Innovate; Intel; Sustainable Energy Authority of Ireland; tire manufacturing giant Bridgestone (which is also the lead sponsor behind the World Solar Challenge); Fidelity Investments; and Irish space-tech EireComposites.

“Timeless hours over the past four years have resulted in this pinnacle of Irish engineering, thanks to the support of our partners, university and the students behind the project,” said Rian Gill, the team principal and lead engineer at DCU Solar Racing.

Jennifer Bruton, the executive dean of the Faculty of Engineering and Computing added: “This project showcases the practical, future-focused, boundary-pushing talent emerging from DCU.

“Beyond competing in international motorsport, these students are proving that sustainable transport solutions are achievable today through dedication, teamwork, multidisciplinary hands-on application and vision.”

Don’t miss out on the knowledge you need to succeed. Sign up for the Daily Brief, Silicon Republic’s digest of need-to-know sci-tech news.

To perform a free reverse phone lookup without hitting paywalls, combine real-time community spam directories, exact-match search engine operators, social messaging app profile checks, and free technical carrier lookup tools. This multi-layered investigation method reveals caller identities, line types, and scam risks without requiring a subscription or credit card.

Quick Take: Reverse Lookup Method Comparison

Different reverse phone lookup methods yield distinct types of data. While community databases highlight telemarketers and scammers quickly, search engines and messaging apps are better suited for identifying unknown individuals.

Prerequisites & Anti-Paywall Red Flags

Before initiating a reverse search, standardizing your input digits improves accuracy across search engines and directory databases. Most reverse search failures happen because the query string omits essential formatting or includes extra characters that break direct database matching.

Standardizing Phone Number Formats Before Searching

Search engines and public databases parse telephone numbers differently depending on how punctuation is used. When preparing a number for analysis, test these common variations:

If you regularly inspect incoming calls on mobile devices, review our reference guide on standard phone number formats to streamline bulk queries across multiple tools.

How to Spot Deceptive “Free” Lookup Traps

The vast majority of commercial “free reverse lookup” websites use aggressive lead-generation mechanics. Commercial background check services like Whitepages paywall mobile subscriber names behind subscription models, limiting free results strictly to landline owner details, general city locations, and carrier line types.

Watch for these common indicator patterns that signal a site will demand payment before delivering usable data:

• Progress bar animations: Simulated loading screens claiming to scan “50 billion public records” or “criminal databases” for a basic phone query. Real database lookups execute in milliseconds.
• Trial subscription lures: Prompts offering a full background report for $1.00 or $5.00. Accepting these trials enrolls your payment card in recurring monthly fees ranging from $19.95 to $34.95.
• Hidden subscriber disclosures: Micro-copy in site footers stating that cellular phone records are protected by telecommunication privacy laws and cannot be provided for free.

Step-by-Step Reverse Phone Lookup Protocol

Follow this multi-tier protocol to trace unknown numbers. If you are dealing with suspected robocalls or telemarketers, start at Step 1. If you are trying to identify a specific personal caller, skip directly to Step 2 and Step 3.

When an unknown caller leaves no voicemail, your first step should be cross-referencing public spam reporting networks. Millions of users submit real-time reports categorizing calls from debt collectors, political campaigns, delivery agents, and financial scams.

1. Open a browser tab and access Truecaller’s web lookup engine. Enter the full 10-digit number with its country code to view caller reputation scores, business names, and user-submitted flags.
2. If the caller operates within the United Kingdom or Europe, search the Who Called Me database to view community comments detailing exact call scripts and caller behavior patterns.
3. For US-based incoming calls, cross-reference the number against public regulatory indices using tools like Block Guard’s FTC complaint search to verify whether the line has been cited in official federal telemarketing violation reports.

Expected Outcome: If the number belongs to a call center or scam campaign, community directories will surface the caller’s business identity, operational category, and risk score instantly without requiring account creation.

Step 2: Execute Exact-Match Google OSINT Searches

If community directories return no results, the number likely belongs to a private individual or local small business. General search engine queries often obscure specific phone matches under paid advertising results. Using exact-match search operators (open-source intelligence dorking) bypasses sponsored ads and forces the search engine to return indexed pages containing that explicit digit string.

1. Search exact digit strings by wrapping the number in quotation marks: "123-456-7890" and "1234567890".
2. Restrict results to specific social platforms and professional directories by appending domain parameters: site:facebook.com "123-456-7890" or site:linkedin.com "123-456-7890".
3. Search for associated documents such as public real estate listings, corporate PDF filings, or classified ads: filetype:pdf "123-456-7890".

Applying structured advanced search operators exposes forgotten forum postings, old Craigslist listings, church newsletters, and municipal public records where individuals published their direct cell numbers online.

According to the official OSINT Industries investigation workflow, testing both national international prefixes and local hyphenated formats across major search engines captures cached web pages that standard search algorithms filter out.

Expected Outcome: Uncovering direct web footprints connecting the number to real names, personal blog posts, business registration documents, or historical real estate listings.

Step 3: Cross-Reference Social Messaging Apps

Mobile messaging applications often link telephone numbers directly to user account profiles. By temporarily saving an unknown number into your device contacts, you can inspect associated profile pictures, screen names, and bio metadata within privacy-respecting messaging ecosystems.

1. Create a temporary contact entry in your smartphone address book (e.g., “Trace Subject”) and save the unknown number in full international format (+1XXXYYYZZZZ).
2. Open WhatsApp, select the new chat icon, and search for your newly created contact entry. If the contact possesses an active WhatsApp profile, their profile photo, display name, and public “About” text will load automatically.
3. Open Telegram, access the contact sync menu, and check whether an associated account appears. Telegram profiles frequently expose custom user handles, personal avatars, and recent activity statuses.
4. Open Signal to check for public profile names and avatar disclosures.
5. Once your inspection is complete, delete the temporary contact from your address book. You can also safely backup contact lists to ensure sandbox testing does not pollute your main address book sync.

Expected Outcome: High-resolution profile photos, full display names, and personal bio text provided directly by the account owner, effectively confirming who holds the line.

Step 4: Verify Carrier, Location, and Line Type

When web searches and messaging applications reveal no user profiles, auditing the technical infrastructure of the phone line provides critical answers. Knowing whether a number is a physical landline, a cellular phone, or a virtual internet line dictates how you should handle incoming calls.

1. Navigate to a free telecommunication lookup utility. Query the number using the IPQualityScore phone carrier lookup tool to fetch underlying network routing records.
2. Inspect the line type specification: Landline, Mobile/Wireless, Fixed VoIP, or Non-Fixed VoIP.
3. Review the original issuing carrier (e.g., Verizon Wireless, AT&T, T-Mobile, Bandwidth.com, or Twilio) and verify the original geographical rate center (city and state).

Identifying non-fixed virtual phone line services confirms that the caller operates through an internet application rather than a physical SIM card or home landline, which is a common characteristic of commercial call centers and automated web applications.

Expected Outcome: Clear determination of line type, network operator, origin location, and line activity status, establishing whether the caller is using a physical telephone or a virtual web application.

Verification: Confirming Identities and Detecting Spoofing

Gathering a name or carrier record is only effective if you verify that the information actually matches the person on the other end of the line. Misidentification occurs easily when relying on a single data point.

Cross-Referencing Multi-Source Signals

Never accept a single search result as absolute proof of identity. Validate your findings by comparing at least two independent data channels:

• Match the geographical area code and carrier location from Step 4 against the physical address details discovered via search dorking in Step 2.
• Confirm that the display name exposed in messaging apps (Step 3) aligns with public business directory records or social profiles found in Step 2.
• Verify that the line type reported by carrier utilities matches the caller’s behavior (for instance, a local bank calling from a non-fixed VoIP line warrants extra scrutiny).

Detecting Caller ID Spoofing

Caller ID spoofing occurs when a caller alters the outgoing call signal to display a fake number on your phone screen. Scammers frequently practice “neighbor spoofing,” disguising outgoing calls with your local area code and exchange prefix to increase answer rates.

To guard against spoofed calls, implement these defense measures:

• Never rely solely on incoming Caller ID: Seeing a legitimate hospital, police department, or utility company name on your caller ID screen does not prove the call originated from that organization.
• Perform outbound verification callbacks: If an incoming call demands urgent payment or sensitive information, hang up immediately. Search for the official published phone number of the institution independently and initiate an outbound call directly.
• Review established defensive strategies: Read our complete guide on identifying caller ID spoofing tactics to learn how modern call authentication standards (STIR/SHAKEN) handle call routing verification.

Troubleshooting Common Lookup Failures

Even structured investigations can encounter dead ends. Here is how to resolve common reverse phone lookup roadblocks.

No Results Found Across Directories

If every public directory, search engine, and messaging application returns zero records, you are likely dealing with one of these scenarios:

• Newly provisioned mobile lines: Newly assigned cellular numbers take several months to accumulate public digital footprints or appear in cached search engine indexes.
• Strict privacy settings: Mobile users who uncheck “Discoverability by Phone Number” in their social app settings will not appear during messaging app contact syncs.
• Unlisted private numbers: Individuals who never publish their contact details on public websites or e-commerce platforms will leave no indexable search engine footprint.

Handling VoIP and Virtual Burner Numbers

When carrier lookup utilities identify a line as “Non-Fixed VoIP” (provisioned by services like Google Voice, TextNow, Pinger, or Skype), individual owner details are shielded behind service provider privacy protections. Non-fixed VoIP numbers can be created in seconds from anywhere in the world, making them popular for privacy-conscious individuals as well as telemarketers.

If you encounter a persistent virtual line that cannot be traced to a real person, consult our overview of temporary virtual phone numbers to understand how disposable internet numbers operate and how privacy apps handle user registration data.

Where This Approach Has Limits: Legal & Privacy Boundaries

Understanding the legal limits of public data retrieval prevents wasted effort and keeps your expectations realistic. Cellular carriers in North America and Europe are legally restricted from publishing master subscriber directories under telecommunication privacy regulations, including the Fair Credit Reporting Act (FCRA) and the General Data Protection Regulation (GDPR).

Legitimate, 100% free reverse phone lookup techniques rely entirely on public OSINT footprints, real-time spam reporting feeds, and opt-in user profiles. Websites promising to reveal private cellular billing addresses, SSNs, or credit histories for free are deceptive lead generators designed to sell recurring monthly subscriptions.

Key Takeaways

Frequently Asked Questions

PayPal reportedly rejected a takeover offer last month over concerns it was being undervalued.

Plans for a joint acquisition of PayPal have fallen through, according to Bloomberg News, weeks after the company’s board reportedly rejected a $53bn-plus offer from Stripe and US private equity firm Advent International.

Talks of a potential Stripe acquisition of PayPal have swirled for months. According to reports last month, Stripe and Advent offered to buy PayPal at $60.50 per share, which would have valued the fintech at more than $53bn and represented a 28pc premium to its share price in mid-July.

That offer was, however, reportedly rejected by PayPal’s board over concerns that it undervalued the company. Sources told Bloomberg that Stripe and Advent have now abandoned talks.

Founded in the late 1990s, PayPal has struggled in recent years to modernise against emerging rivals in the payments space such as Apple, Google and Stripe. PayPal’s shares have dropped dramatically over recent years as a result, but picked up somewhat last month after promising reports of a takeover by the $159bn Stripe.

PayPal’s shares have jumped nearly 10pc over the last month, now giving the company a market capitalisation of $52.5bn – up from roughly $43bn in February, when Bloomberg first reported on a potential acquisition. The fintech also recorded a 5pc growth in net revenue in the second quarter.

PayPal and Stripe would each benefit from the possible acquisition, according to Chris Jones, managing director at PSE Consulting.

“PayPal’s wallet could build on the early success of Link, Stripe’s consumer-facing accelerated checkout, which already counts more than 200m consumer accounts, and would create further opportunities to exploit Stripe’s $1.1bn investment in stablecoin infrastructure through its purchase of Bridge,” he told SiliconRepublic.com last month.

The US fintech brought in HP’s Enrique Lores as its new CEO earlier this year, replacing Alex Chriss, whose work was “not in line” with board expectations. By June, PayPal had reportedly planned to shut down its venture capital arm.

Stripe, meanwhile, is investing heavily in product development and making strategic acquisitions, including the programmable wallet company Privy, stablecoin orchestration platform Bridge and billing platform Metronome.

It recently announced that it is acquiring large language model marketplace OpenRouter at a reported cost of between $7bn and $10bn as part of efforts to help businesses optimise token costs.

Don’t miss out on the knowledge you need to succeed. Sign up for the Daily Brief, Silicon Republic’s digest of need-to-know sci-tech news.

In a nutshell: Cloudflare has cut the memory used by the DNS cache behind its 1.1.1.1 resolver by more than half, freeing about 100TB of RAM across its network. The company did not replace server hardware or remove memory modules. Instead, engineers changed how cached DNS data is stored in software.

The optimization work was centered on Big Pineapple, Cloudflare’s DNS caching platform behind the popular 1.1.1.1 resolver, DNS Firewall, and several other DNS services they offer. In a technical blog post, systems engineer Sebastiaan Neuteboom detailed five changes to the Rust codebase that shrank a typical cache entry from 953 bytes to 420 bytes.

The changes also made the cache faster. Cloudflare reported that insert throughput rose from 625,000 to 893,000 entries per second, while lookup latency fell from 828 nanoseconds to 670 nanoseconds. During the rollout, from mid-May to early July, p99 memory use per instance dropped from 9.3GB to 5.3GB.

Cloudflare says Big Pineapple holds more than 250 billion DNS entries at any given time, and at that scale even small amounts of wasted memory add up fast. The company estimates that a single unnecessary byte in each cache entry costs more than 250GB across its fleet.

Big Pineapple, Cloudflare’s DNS caching platform, was redesigned in Rust to free about 100TB of RAM.

One of the biggest changes involved Rust’s Vec and String types. Those containers are designed to grow, so they store capacity data in addition to the data itself. But DNS records do not need to expand after they enter the cache. Cloudflare replaced those structures with fixed-size boxed slices, eliminating metadata that was no longer useful. The company said that change alone saved more than 15TB of RAM.

Engineers also rethought how DNS responses are laid out in memory. Big Pineapple used to store three separate record lists per response. The new design puts the records in one buffer and identifies them with two-byte offsets.

The cache no longer retains owner names when they simply repeat the queried domain. Cloudflare rebuilds those names when it serves the response. It also now stores record data as length-prefixed raw wire-format bytes. That change addresses a mismatch in the earlier design. A four-byte IPv4 A record occupied the same 144 bytes as the largest DNS record type Cloudflare caches, the relatively uncommon NAPTR record. Storing raw data in a variable-length format reduces that waste.

The 100TB of RAM Cloudflare recovered across its fleet is roughly equal to the memory in 130 of its Gen 13 servers, each of which carries 768GB of DDR5-6400. The company had considered a 1,152GB configuration for that server generation but passed on it after weighing the cost of higher-capacity RAM.

With the RAM savings, Cloudflare plans to allocate the memory to larger DNS caches. Keeping more records locally should improve cache hit rates and reduce the traffic it sends to authoritative DNS servers.

This project follows another major memory-efficiency effort completed last year, when Cloudflare rewrote its FL2 request-handling layer in Rust. That’s probably a good way to spend resources and squeeze more out of its existing infrastructure as server memory gets pricier.

Apart from the new chipset, the camera upgrades, and Gemini Intelligence, the Pixel 11 Pro shipped with something that turned a lot of heads, in enthusiasm no less: the RGB light module on the back called HiLight. 

Before Google announced the feature, I was actually excited about it, thinking about all the potential use cases; the light could have been a subtle notification queue for users, one that doesn’t compel them to unlock the phone right away. However, Google tied the hardware to two use cases: Gemini interactions and calls from favorite contacts.

That is exactly why tech content creator @Dhananjay_Tech (DhananjayBhosale) created an app called HiLight Studio, with a simple pitch: unlock HiLight’s true potential by opening it up to third-party apps and letting you have some fun with it. After spending a few days with the app on a Pixel 11 Pro XL, I have some thoughts, both about what the HiLight is actually capable of, and how much Google actually left on the table with it.

That’s where HiLight Studio comes in

On the home page, you can try out plenty of HiLight effects. The Rainbow effect comes closest to what we’ve seen in the promotional materials so far, with the modules lighting up in a rotating gradient. You also get five other effects to choose from: Random, Comet, Pulse, Breathe, and Wave. While this page is called Live (designated at the bottom of the screen), the Style page to the right lets you enable HiLight as an always-on light. 

You can also choose different ways you want the LED modules to light up, including a gradient finish (with the option to select the start/end color), a breathing look (with the option to set the timing per cycle), and more. 

There’s an Apps section as well, wherein you can customize how the HiLight module glows up upon receiving a notification from an app. In my case, I’ve set a Chasing green light for WhatsApp, set as “on notification” rather than “while open.” Similarly, you can also create per-app rules for Instagram, Messenger, Teams, Gmail, or Slack.

This is where the hardware finally makes sense

This is one of the most intuitive and natural use cases of HiLight in my opinion, something that I’d like to remain this way. For what it’s worth, the app genuinely makes Google’s HiLight module interesting. It turns the boring system implementation into something that I always imagined it would be: a glanceable notification system.

Here’s the catch: enabling wireless debugging locks me out of the banking and payment apps I use daily, for security reasons that are frankly fair, not paranoid. So even though I like what HiLight Studio does, I can’t run it full-time. Second, and more importantly, actually getting the app working is a genuinely arduous process for a regular user.

Getting to what Google left behind is more tedious than it should be

You need two apps installed: HiLight Studio and Shizuku. First, enable Developer Options by tapping the build number seven times under “About phone,” because apparently that’s still how we’re gatekeeping settings in 2026. Then enable wireless debugging, install Shizuku, pair it using the six-digit code from the notification, and tap “Start.” 

Shizuku, for the uninitiated, lets third-party apps borrow first-party system permissions, which in this case means the HiLight module. It’s only on the Play Store for Android 16 devices, so it wasn’t even available for my Pixel 11 Pro XL running Android 17, forcing a sideload instead. However, some of you might already know that the app was recently exploited by RedHook malware, which would also keep most users from installing it.

From there, open HiLight Studio, head to Setup, and under “Privileged access,” select Shizuku. Grant notification access too. Get everything right, and you’ll see a small “8 LEDs · Shizuku” confirmation appear, followed by one final toggle next to “System has HiLight” that unlocks the effects at the bottom. 

Getting here is easier said than done

You see? It took me around 150 words to explain how the process works, and it would probably take you around 10 to 15 minutes to set everything up, provided you’re familiar with Developer Options and apps like Shizuku.

The app works about 70 to 80% of the time, but sometimes a WhatsApp notification doesn’t trigger the effect. Further, rebooting the phone disrupts the connection between HiLight Studio and Shizuku, and you have to re-establish it to use the lights.

I’d have to give up access to the payment apps I use every day, keep wireless debugging enabled, and rely on a third-party bridge that might or might not be a security issue, all to unlock functionality that Google could have offered natively. These aren’t things that a regular user would want to do on their smartphone.

For me, HiLight Studio proves what Google is missing

I really appreciate the creator of the app, as it lets users explore HiLight’s true potential. However, a third-party app can’t beat a native, system-level implementation that would make the feature much more useful and worthwhile for everyone, not just enthusiasts.

The app simply proves that the hardware can do much more than Google currently allows, and that’s the key takeaway. If someone at Google is reading this, I genuinely hope you’re planning to add some fun HiLight functionality in one of the upcoming Pixel Drops, because otherwise, this feels like a missed opportunity.